From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752174AbdJTIFJ (ORCPT ); Fri, 20 Oct 2017 04:05:09 -0400 Received: from mx2.suse.de ([195.135.220.15]:46903 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752052AbdJTIFG (ORCPT ); Fri, 20 Oct 2017 04:05:06 -0400 Date: Fri, 20 Oct 2017 10:05:01 +0200 From: Petr Mladek To: Calvin Owens Cc: Sergey Senozhatsky , Steven Rostedt , linux-api@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, kernel-team@fb.com Subject: Re: [PATCH 1/3] printk: Introduce per-console loglevel setting Message-ID: <20171020080501.GD29163@pathway.suse.cz> References: <08c1dc1a96afd6b6aecc5ff3c7c0e62c36670893.1506644730.git.calvinowens@fb.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. Best Regards, Petr