linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/5] console: Drop double check for console_drivers being non-NULL
Date: Wed, 29 Jan 2020 14:24:27 +0100	[thread overview]
Message-ID: <20200129132427.bg774jfgbvm33s5w@pathway.suse.cz> (raw)
In-Reply-To: <20200127114719.69114-2-andriy.shevchenko@linux.intel.com>

On Mon 2020-01-27 13:47:16, Andy Shevchenko wrote:
> There is no need to explicitly check for console_drivers to be non-NULL
> since for_each_console() does this.
> 
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

Nice catch.

Reviewed-by: Petr Mladek <pmladek@suse.com>

There is a candidate for another patch, see the note below.

> ---
> v3: no changes
>  kernel/printk/printk.c | 16 ++++++----------
>  1 file changed, 6 insertions(+), 10 deletions(-)
> 
> diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
> index fada22dc4ab6..51337ed426e0 100644
> --- a/kernel/printk/printk.c
> +++ b/kernel/printk/printk.c
> @@ -2653,18 +2650,17 @@ void register_console(struct console *newcon)
>  	struct console_cmdline *c;
>  	static bool has_preferred;
>  
> -	if (console_drivers)
> -		for_each_console(bcon)
> -			if (WARN(bcon == newcon,
> -					"console '%s%d' already registered\n",
> -					bcon->name, bcon->index))
> -				return;
> +	for_each_console(bcon) {
> +		if (WARN(bcon == newcon, "console '%s%d' already registered\n",
> +					 bcon->name, bcon->index))
> +			return;
> +	}
>  
>  	/*
>  	 * before we register a new CON_BOOT console, make sure we don't
>  	 * already have a valid console
>  	 */
> -	if (console_drivers && newcon->flags & CON_BOOT) {
> +	if (newcon->flags & CON_BOOT) {
>  		/* find the last or real console */

Note: This comment is misleading. I would just remove it.

>  		for_each_console(bcon) {
>  			if (!(bcon->flags & CON_BOOT)) {

Best Regards,
Petr

  reply	other threads:[~2020-01-29 13:24 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-27 11:47 [PATCH v3 1/5] console: Don't perform test for CON_BRL flag Andy Shevchenko
2020-01-27 11:47 ` [PATCH v3 2/5] console: Drop double check for console_drivers being non-NULL Andy Shevchenko
2020-01-29 13:24   ` Petr Mladek [this message]
2020-01-27 11:47 ` [PATCH v3 3/5] console: Use for_each_console() helper in unregister_console() Andy Shevchenko
2020-01-29 14:11   ` Petr Mladek
2020-01-27 11:47 ` [PATCH v3 4/5] console: Avoid positive return code from unregister_console() Andy Shevchenko
2020-01-28  4:43   ` Sergey Senozhatsky
2020-01-28  9:22     ` Andy Shevchenko
2020-01-28  9:25       ` Sergey Senozhatsky
2020-01-28  9:37       ` Sergey Senozhatsky
2020-01-28  9:52         ` Andy Shevchenko
2020-01-30  9:04   ` Petr Mladek
2020-01-30  9:58     ` Andy Shevchenko
2020-01-30 12:22       ` Petr Mladek
2020-01-30 13:13         ` Andy Shevchenko
2020-01-27 11:47 ` [PATCH v3 5/5] console: Introduce ->exit() callback Andy Shevchenko
2020-01-28  5:17   ` Sergey Senozhatsky
2020-01-28  9:44     ` Andy Shevchenko
2020-01-29 13:41       ` Sergey Senozhatsky
2020-01-29 14:25         ` Andy Shevchenko
2020-01-29 15:12           ` Sergey Senozhatsky
2020-01-29 16:50             ` Sergey Senozhatsky
2020-01-30 13:14               ` Andy Shevchenko
2020-01-30 13:22           ` Petr Mladek
2020-01-30 13:39             ` Andy Shevchenko
2020-01-30  9:09   ` Petr Mladek
2020-01-30 10:01     ` Andy Shevchenko
2020-01-29 12:29 ` [PATCH v3 1/5] console: Don't perform test for CON_BRL flag Petr Mladek

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=20200129132427.bg774jfgbvm33s5w@pathway.suse.cz \
    --to=pmladek@suse.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sergey.senozhatsky@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).