From: John Ogness <john.ogness@linutronix.de>
To: Petr Mladek <pmladek@suse.com>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
Marcos Paulo de Souza <mpdesouza@suse.com>,
Chris Down <chris@chrisdown.name>,
Naveen Kumar Chaudhary <naveen.osdev@gmail.com>,
linux-kernel@vger.kernel.org, Petr Mladek <pmladek@suse.com>
Subject: Re: [PATCH v5 04/16] printk: Separate code for adding/updating preferred console metadata
Date: Tue, 27 Oct 2026 13:11:33 +0106 [thread overview]
Message-ID: <87cxsv4acy.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <20260929120546.328616-5-pmladek@suse.com>
On 2026-09-29, Petr Mladek <pmladek@suse.com> wrote:
> The logic for adding or updating a preferred console is currently
> duplicated within __add_preferred_console(), making the code difficult
> to follow and prone to consistency issues.
>
> Split the code for adding or updating entries to avoid code duplication.
> Make it clear what operations are done only for new entries.
>
> Use this opportunity and replace an int with an unsigned int for
> iterating over the preferred_consoles array.
>
> It is a preparation step before adding more consistency checks.
> No intended functional changes.
>
> Signed-off-by: Petr Mladek <pmladek@suse.com>
Reviewed-by: John Ogness <john.ogness@linutronix.de>
Some minor comments below...
> diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
> index c3e50f19a32b..174aee533a53 100644
> --- a/kernel/printk/printk.c
> +++ b/kernel/printk/printk.c
> @@ -2577,35 +2584,56 @@ static int __add_preferred_console(const char *name, const short idx,
> if (name && idx < 0)
> return -EINVAL;
>
> + if (!pc->name[0] && !pc->devname[0])
> + is_new_entry = true;
> +
> + if (is_new_entry) {
> + if (devname)
> + strscpy(pc->devname, devname);
> + if (name)
> + strscpy(pc->name, name);
> + pc->index = idx;
> + }
> +
> /*
> - * See if this tty is not yet registered, and
> - * if we have a slot free.
> + * Historically, the preferred options are stored only by the first
> + * caller who prefers the particular console.
> */
> + if (is_new_entry) {
> + pc->options = options;
> + braille_set_options(pc, brl_options);
> + }
> +
> + if (!brl_options)
> + preferred_dev_console = i;
> +
> + if (user_specified) {
Here you drop the comments:
/*
* @pc console was defined by the user on the command line.
* Do not clear when added twice also by SPCR or the device tree.
*/
> + pc->user_specified = true;
And here you drop the comments:
/* At least one console defined by the user on the command line. */
> + console_set_on_cmdline = 1;
> + }
The comments seem useful to help track all this. I do not see this
information preserved anywhere by the end of your series. But you have a
better understanding of the big picture. If you think the comments are
insignificant and/or misleading, I am fine with you dropping them.
John
next prev parent reply other threads:[~2026-10-27 12:05 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 12:05 [PATCH v5 00/16] printk: Clean up preferred console handling Petr Mladek
2026-09-29 12:05 ` [PATCH v5 01/16] printk: Rename struct console_cmdline to preferred_console Petr Mladek
2026-10-29 7:03 ` Chris Down
2026-11-03 15:16 ` Petr Mladek
2026-09-29 12:05 ` [PATCH v5 02/16] printk: Rename preferred_console to preferred_dev_console Petr Mladek
2026-09-29 12:05 ` [PATCH v5 03/16] printk: Cleanup _braille_(un)register_console() wrappers Petr Mladek
2026-09-29 12:05 ` [PATCH v5 04/16] printk: Separate code for adding/updating preferred console metadata Petr Mladek
2026-10-27 12:05 ` John Ogness [this message]
2026-11-03 15:57 ` Petr Mladek
2026-10-29 7:05 ` Chris Down
2026-11-03 16:12 ` Petr Mladek
2026-09-29 12:05 ` [PATCH v5 05/16] printk: Prefer the console either via name or devname exclusively Petr Mladek
2026-10-27 12:14 ` John Ogness
2026-10-29 7:06 ` Chris Down
2026-09-29 12:05 ` [PATCH v5 06/16] printk: Check that index is not defined when a console is preferred via devname Petr Mladek
2026-10-27 18:08 ` John Ogness
2026-10-29 7:07 ` Chris Down
2026-09-29 12:05 ` [PATCH v5 07/16] printk: Ensure consistent name and devname when updating preferred console Petr Mladek
2026-10-29 7:09 ` Chris Down
2026-11-03 17:08 ` Petr Mladek
2026-09-29 12:05 ` [PATCH v5 08/16] printk: Do not quietly ignore adding entry for a preferred console when there is no space Petr Mladek
2026-10-29 7:10 ` Chris Down
2026-10-29 16:23 ` John Ogness
2026-09-29 12:05 ` [PATCH v5 09/16] printk: Allow to override options via the command line Petr Mladek
2026-10-29 7:13 ` Chris Down
2026-10-30 17:04 ` John Ogness
2026-11-04 12:55 ` Petr Mladek
2026-09-29 12:05 ` [PATCH v5 10/16] printk: Allow to debug misuse of add_or_update_preferred_console() Petr Mladek
2026-10-29 7:13 ` Chris Down
2026-09-29 12:05 ` [PATCH v5 11/16] console/braille: Lock console->setup() call during the registration Petr Mladek
2026-10-29 7:15 ` Chris Down
2026-11-04 14:21 ` Petr Mladek
2026-09-29 12:05 ` [PATCH v5 12/16] printk: Separate code for enabling console Petr Mladek
2026-10-29 7:15 ` Chris Down
2026-09-29 12:05 ` [PATCH v5 13/16] printk: Try to register each console as Braille first Petr Mladek
2026-10-29 7:17 ` Chris Down
2026-11-05 17:13 ` Petr Mladek
2026-11-06 11:33 ` Petr Mladek
2026-09-29 12:05 ` [PATCH v5 14/16] printk: Do not set Braille console as preferred_console Petr Mladek
2026-10-29 7:19 ` Chris Down
2026-11-06 14:21 ` Petr Mladek
2026-09-29 12:05 ` [PATCH v5 15/16] printk: Modify try_enable_default_console() to return error/success Petr Mladek
2026-10-29 7:20 ` Chris Down
2026-09-29 12:05 ` [PATCH v5 16/16] printk: Try enable preferred consoles only when there are any Petr Mladek
2026-10-29 7:20 ` Chris Down
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=87cxsv4acy.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=chris@chrisdown.name \
--cc=linux-kernel@vger.kernel.org \
--cc=mpdesouza@suse.com \
--cc=naveen.osdev@gmail.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.