From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Petr Mladek <pmladek@suse.com>
Cc: John Ogness <john.ogness@linutronix.de>,
Chris Down <chris@chrisdown.name>,
linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
kernel-team@fb.com
Subject: Re: design: was: Re: [RFC PATCH v2] printk: console: Allow each console to have its own loglevel
Date: Mon, 11 Jul 2022 19:17:27 +0900 [thread overview]
Message-ID: <Ysv4t6ofeq6tL7Oj@google.com> (raw)
In-Reply-To: <YsvgDRQICB3nEc1l@alley>
On (22/07/11 10:32), Petr Mladek wrote:
> On Fri 2022-07-08 21:10:35, John Ogness wrote:
> > On 2022-07-08, Petr Mladek <pmladek@suse.com> wrote:
> > > The console-specific loglevel might be set by:
> > >
> > > + "console=device,options/loglevel" kernel parameter at boot time
> >
> > I ask if we avoid the use of "/loglevel" and instead use a generic
> > scheme of:
> >
> > console=device,option,option,option
> >
> > Of course, it would mean that the type of option would need to be
> > specified. Something like:
> >
> > console=ttyS0,115200n8,loglevel=3
>
> I like this. It is longer but it makes the meaning very obvious.
Looks beautiful.
next prev parent reply other threads:[~2022-07-11 11:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 12:57 [RFC PATCH v2] printk: console: Allow each console to have its own loglevel Chris Down
2022-05-20 16:06 ` Rik van Riel
2022-07-07 14:38 ` Petr Mladek
2022-07-13 14:32 ` Chris Down
2022-05-21 18:51 ` Greg Kroah-Hartman
2022-05-21 19:23 ` Chris Down
2022-05-23 13:09 ` Vincent Whitchurch
2022-05-23 14:24 ` Chris Down
2022-06-16 15:57 ` Chris Down
2022-07-08 15:23 ` design: was: " Petr Mladek
2022-07-08 19:04 ` John Ogness
2022-07-11 8:32 ` Petr Mladek
2022-07-11 10:17 ` Sergey Senozhatsky [this message]
2022-07-13 14:50 ` Chris Down
2022-07-13 14:49 ` Chris Down
2022-07-14 15:44 ` Petr Mladek
2022-07-15 12:49 ` Petr Mladek
2022-07-15 13:00 ` Chris Down
2022-07-19 12:11 ` Chris Down
2022-07-19 13:00 ` 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=Ysv4t6ofeq6tL7Oj@google.com \
--to=senozhatsky@chromium.org \
--cc=chris@chrisdown.name \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=john.ogness@linutronix.de \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.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 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.