From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Petr Mladek <pmladek@suse.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Peter Zijlstra <peterz@infradead.org>,
John Ogness <john.ogness@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/3] printk/console: Fix preferred console handling
Date: Mon, 17 Feb 2020 22:03:08 +0900 [thread overview]
Message-ID: <20200217130308.GA447@jagdpanzerIV.localdomain> (raw)
In-Reply-To: <20200213095133.23176-1-pmladek@suse.com>
On (20/02/13 10:51), Petr Mladek wrote:
> Hi,
>
> I send this on behalf of Benjamin who is traveling at the moment.
> It is an interesting approach to long terms problems with matching
> the console preferred on the command line.
>
> Changes against v3:
>
> + better check when accepting pre-enabled consoles
> + correct reasoning in the 3rd patch
> + update a comment of CON_CONSDEV definition
> + fixed checkpatch warnings
Looks good to me,
Reviewed-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
-ss
next prev parent reply other threads:[~2020-02-17 13:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 9:51 Petr Mladek
2020-02-13 9:51 ` [PATCH v4 1/3] printk: Move console matching logic into a separate function Petr Mladek
2020-02-13 9:51 ` [PATCH v4 2/3] printk: Fix preferred console selection with multiple matches Petr Mladek
2020-02-13 9:51 ` [PATCH v4 3/3] printk: Correctly set CON_CONSDEV even when preferred console was not registered Petr Mladek
2020-02-17 13:03 ` Sergey Senozhatsky [this message]
2020-02-18 9:52 ` [PATCH v4 0/3] printk/console: Fix preferred console handling Petr Mladek
2020-02-20 1:44 ` Benjamin Herrenschmidt
2020-02-27 22:14 ` Benjamin Herrenschmidt
2020-02-28 14:58 ` Petr Mladek
2020-02-29 5:47 ` Sergey Senozhatsky
2020-03-02 4:48 ` Benjamin Herrenschmidt
2020-04-22 23:21 ` Benjamin Herrenschmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200217130308.GA447@jagdpanzerIV.localdomain \
--to=sergey.senozhatsky@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®