[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171219094052.15a94379@gandalf.local.home>
Date: Tue, 19 Dec 2017 09:40:52 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
Cc: Petr Mladek <pmladek@...e.com>, Tejun Heo <tj@...nel.org>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Jan Kara <jack@...e.cz>,
Andrew Morton <akpm@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>,
Rafael Wysocki <rjw@...ysocki.net>,
Pavel Machek <pavel@....cz>,
Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>,
linux-kernel@...r.kernel.org
Subject: Re: [RFC][PATCHv6 00/12] printk: introduce printing kernel thread
On Tue, 19 Dec 2017 13:58:46 +0900
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com> wrote:
> so you are not convinced that my scenarios real/matter; I'm not
Well, not with the test module. I'm looking for actual code in the
upstream kernel.
> convinced that I have stable and functional boards with this patch ;)
> seems that we are coming to a dead end.
Can I ask, is it any worse than what we have today?
>
> for the record,
> I'm not going to block the patch if you want it to be merged.
Thanks,
-- Steve
Powered by blists - more mailing lists