From: Adam Simonelli <adamsimonelli@gmail.com>
To: Petr Mladek <pmladek@suse.com>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
Jiri Slaby <jirislaby@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
John Ogness <john.ogness@linutronix.de>,
Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: Re: [PATCH v8 1/4] ttynull: Always initialize console index to -1
Date: Thu, 13 Mar 2025 08:09:36 -0400 [thread overview]
Message-ID: <4810112.n0HT0TaD9V@nerdopolis2> (raw)
In-Reply-To: <Z9Gcg-iMMCAhLUJf@pathway.suse.cz>
On Wednesday, March 12, 2025 10:38:59 AM EDT Petr Mladek wrote:
> On Mon 2025-03-10 23:31:30, adamsimonelli@gmail.com wrote:
> > From: Adam Simonelli <adamsimonelli@gmail.com>
> >
> > This allows ttynull to be considered in console selection.
>
> This is not true. It should be possible to register ttynull even
> when .index == 0.
>
> The .index is important only for drivers which support more devices,
> e.g. the serial port or virtual terminal.
>
> >
> > Suggested-by: Petr Mladek <pmladek@suse.com>
> > Signed-off-by: Adam Simonelli <adamsimonelli@gmail.com>
> > ---
> > drivers/tty/ttynull.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/tty/ttynull.c b/drivers/tty/ttynull.c
> > index 6b2f7208b564..d8b51edde628 100644
> > --- a/drivers/tty/ttynull.c
> > +++ b/drivers/tty/ttynull.c
> > @@ -57,6 +57,7 @@ static struct tty_driver *ttynull_device(struct console *c, int *index)
> > static struct console ttynull_console = {
> > .name = "ttynull",
> > .device = ttynull_device,
> > + .index = -1,
>
> There is only one "/dev/ttynull". And its index is initialized to "0".
> At least it seems to be the last parameter in:
>
> static int __init ttynull_init(void)
> {
> [...]
> tty_port_link_device(&ttynull_port, driver, 0);
> [...]
> }
>
> So, I believe this it should be perfectly fine to keep the default "0"
> here. Note that it is special for ttynull because it is only one...
>
> IMHO, this patch adds more harm than good :-)
>
> Best Regards,
> Petr
>
Understood, thanks for the explanation about that.
next prev parent reply other threads:[~2025-03-13 12:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 3:31 [PATCH v8 0/4] Optionally allow ttynull to be selected as a default console adamsimonelli
2025-03-11 3:31 ` [PATCH v8 1/4] ttynull: Always initialize console index to -1 adamsimonelli
2025-03-12 14:38 ` Petr Mladek
2025-03-13 12:09 ` Adam Simonelli [this message]
2025-03-11 3:31 ` [PATCH v8 2/4] ttynull: Add an option to allow ttynull to be used as a console device adamsimonelli
2025-03-12 15:37 ` Petr Mladek
2025-03-11 3:31 ` [PATCH v8 3/4] tty: Change order of ttynull to be linked sooner if enabled as a console adamsimonelli
2025-03-11 3:31 ` [PATCH v8 4/4] Documentation/serial-console: Document CONFIG_NULL_TTY_DEFAULT_CONSOLE adamsimonelli
2025-03-12 15:40 ` Petr Mladek
2025-03-11 19:50 ` [PATCH v8 0/4] Optionally allow ttynull to be selected as a default console Andy Shevchenko
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=4810112.n0HT0TaD9V@nerdopolis2 \
--to=adamsimonelli@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--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