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>,
linux-kernel@vger.kernel.org, Petr Mladek <pmladek@suse.com>
Subject: Re: [PATCH v2 3/9] printk: Separate code for adding/updating preferred console metadata
Date: Fri, 15 May 2026 12:36:58 +0206 [thread overview]
Message-ID: <87lddl6k2l.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <87o6ih6kfh.fsf@jogness.linutronix.de>
On 2026-05-15, John Ogness <john.ogness@linutronix.de> wrote:
>> + if (!pc->name[0]) {
>> + strscpy(pc->name, name);
>> + pc->index = idx;
>
> Here is the copied code. This block is about setting the name.
>
>> + } else if (strcmp(pc->name, name) != 0 || pc->index != idx) {
>> + pr_err("Updating a preferred console with an invalid name or index: %s%d vs. %s%d\n",
>> + pc->name, pc->index, name, idx);
>> + return -EINVAL;
>> + }
>> + }
>
> I would put the index setting here as it is relevant regardless of how
> the devname or name was updated.
>
> pc->index = idx;
Ah, I guess you only wanted to update @index if it is a new entry
(because otherwise it will already have the value of @idx).
If you want to keep the index setting in the devname and name blocks,
maybe just adding a comment to clarify it is a new entry:
if (!pc->devname[0]) {
/* This is a new entry */
strscpy(pc->devname, devname);
pc->index = idx;
...
if (!pc->name[0]) {
/* This is a new entry */
strscpy(pc->name, name);
pc->index = idx;
John
next prev parent reply other threads:[~2026-05-15 10:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260423130015.85175-1-pmladek@suse.com>
[not found] ` <20260423130015.85175-4-pmladek@suse.com>
2026-05-05 17:47 ` [PATCH v2 3/9] printk: Separate code for adding/updating preferred console metadata Marcos Paulo de Souza
2026-05-15 10:23 ` John Ogness
2026-05-15 10:30 ` John Ogness [this message]
[not found] ` <20260423130015.85175-6-pmladek@suse.com>
2026-05-05 17:56 ` [PATCH v2 5/9] printk: Separate code for enabling console Marcos Paulo de Souza
2026-05-15 12:57 ` John Ogness
[not found] ` <20260423130015.85175-2-pmladek@suse.com>
2026-05-08 14:22 ` [PATCH v2 1/9] printk: Rename struct console_cmdline to preferred_console John Ogness
[not found] ` <20260423130015.85175-3-pmladek@suse.com>
2026-05-15 9:07 ` [PATCH v2 2/9] printk: Rename preferred_console to preferred_dev_console John Ogness
[not found] ` <20260423130015.85175-5-pmladek@suse.com>
2026-05-15 12:51 ` [PATCH v2 4/9] printk: Cleanup _braille_(un)register_console() wrappers John Ogness
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=87lddl6k2l.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=chris@chrisdown.name \
--cc=linux-kernel@vger.kernel.org \
--cc=mpdesouza@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox