[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e757047d-d40a-582b-7c50-b8d8f93a076e@linaro.org>
Date: Fri, 12 May 2017 00:17:18 +0300
From: Aleksey Makarov <aleksey.makarov@...aro.org>
To: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
Cc: Sabrina Dubroca <sd@...asysnail.net>, linux-serial@...r.kernel.org,
linux-kernel@...r.kernel.org, Sudeep Holla <sudeep.holla@....com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Peter Hurley <peter@...leysoftware.com>,
Jiri Slaby <jslaby@...e.com>,
Robin Murphy <robin.murphy@....com>,
Steven Rostedt <rostedt@...dmis.org>,
"Nair, Jayachandran" <Jayachandran.Nair@...ium.com>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Petr Mladek <pmladek@...e.com>
Subject: Re: [PATCH v9 3/3] printk: fix double printing with earlycon
On 05/11/2017 02:32 PM, Sergey Senozhatsky wrote:
> On (05/11/17 17:41), Sergey Senozhatsky wrote:
> [..]
>> Alexey,
>> can we have preferred console at offset 0 (not at console_cmdline_cnt - 1)
>> and restore the previous register_console() iteration order?
>
> btw, what if someone has configured the system as
> console= non-braille non-braille braille non-braille?
> "The last non-braille console is always the preferred one"
> is not true in this case.
I don't quite follow what you think is problem here.
The invariant keeps here, the code makes it always true.
In this case the last console is non-braille and it is preferred.
What is the problem?
Thank you
Aleksey Makarov
Powered by blists - more mailing lists