From: Chris Down <chris@chrisdown.name>
To: John Ogness <john.ogness@linutronix.de>
Cc: Petr Mladek <pmladek@suse.com>,
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: [PATCH v5 2/2] printk: console: Support console-specific loglevels
Date: Tue, 2 May 2023 15:28:24 +0100 [thread overview]
Message-ID: <ZFEeCANq-F7JODRD@chrisdown.name> (raw)
In-Reply-To: <87v8hhs57d.fsf@jogness.linutronix.de>
John Ogness writes:
>I agree that we should go with your 1st proposal. But I would like to
>see some comments added into printk_get_next_message() that only @flags
>and @level may be considered valid.
Thanks, will do for v6.
next prev parent reply other threads:[~2023-05-02 14:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 13:06 [PATCH v5 0/2] printk: console: Per-console loglevels Chris Down
2023-04-25 13:06 ` [PATCH v5 1/2] printk: Do not delay messages which aren't solicited by any console Chris Down
2023-04-26 8:55 ` Petr Mladek
2023-04-25 13:06 ` [PATCH v5 2/2] printk: console: Support console-specific loglevels Chris Down
2023-04-27 13:49 ` Petr Mladek
2023-04-27 15:41 ` John Ogness
2023-05-02 14:28 ` Chris Down [this message]
2023-04-30 17:00 ` [PATCH v5 2/2] printk: console: Remove sysrq exception calumlikesapplepie
2023-05-02 9:23 ` Chris Down
2023-05-02 10:27 ` Petr Mladek
2023-05-02 14:26 ` [PATCH v5 2/2] printk: console: Support console-specific loglevels Chris Down
2023-04-28 16:19 ` kernel test robot
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=ZFEeCANq-F7JODRD@chrisdown.name \
--to=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 \
--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