[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <11bdad91-4cf2-db79-6573-3afdc6bc125d@fb.com>
Date: Fri, 20 Oct 2017 10:33:55 -0700
From: Calvin Owens <calvinowens@...com>
To: Petr Mladek <pmladek@...e.com>
CC: Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Steven Rostedt <rostedt@...dmis.org>,
<linux-api@...r.kernel.org>, <linux-doc@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <kernel-team@...com>
Subject: Re: [PATCH 1/3] printk: Introduce per-console loglevel setting
On 10/20/2017 01:05 AM, Petr Mladek wrote:
> On Thu 2017-10-19 16:40:45, Calvin Owens wrote:
>> On 09/28/2017 05:43 PM, Calvin Owens wrote:
>>> Not all consoles are created equal: depending on the actual hardware,
>>> the latency of a printk() call can vary dramatically. The worst examples
>>> are serial consoles, where it can spin for tens of milliseconds banging
>>> the UART to emit a message, which can cause application-level problems
>>> when the kernel spews onto the console.
>>
>> Any thoughts on this series? Happy to resend again, but if there are no
>> objections I'd love to see it merged sooner rather than later :)
>>
>> Happy to resend too, just let me know.
>
> There is no need to resend the patch. It is on my radar and I am
> going to look at it.
>
> Please, be patient, you hit conference, illness, after vacation
> season. We do not want to unnecessarily delay it but it is
> not a trivial change that might be accepted within minutes.
No worries, just wanted to make sure it hadn't been missed :)
Thanks,
Calvin
> Best Regards,
> Petr
Powered by blists - more mailing lists