lkml.org 
[lkml]   [2016]   [Nov]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: printk considered harmful (was: [TECH TOPIC] asynchronous printk)
On Fri 04-11-16 03:01:31, Sergey Senozhatsky wrote:
> fix a typo
>
> On (11/04/16 02:31), Sergey Senozhatsky wrote:
> [..]
> > #4 console semaphore
> > discussion outcome:
> > we agreed that we can do better here and that it makes sense to do
> ^^^^ IOW, console semaphore thing
> can be improved
>
> > what's been proposed in my slides. but, I keep it as a low priority.
> > frankly. I'd be happy to see #1-#3 in the mainline in 9-12 months.
> ^^^^ #1-#2, of course. but #1 consists
> of 2 steps.
>
> I'm still not entirely sure if I want to split async pintk and printk
> deadlock rework. these things want to come together, for a number of
> reasons. or, at least, push the async printk before printk deadlock
> rework.

Yep, please push async printk patches soon. IMHO there's no reason to wait
with that. You can create a git tree with printk patches and push it directly
to Linus since he seems to be fine with the approach...

Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR

\
 
 \ /
  Last update: 2016-11-04 05:47    [W:0.080 / U:0.020 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site