From: Chris Down <chris@chrisdown.name>
To: Petr Mladek <pmladek@suse.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, kernel-team@fb.com
Subject: [OFFLIST] Re: [RFC PATCH] printk: console: Allow each console to have its own loglevel
Date: Mon, 30 May 2022 11:48:05 +0100 [thread overview]
Message-ID: <YpSg5dsQTDX/OsvI@chrisdown.name> (raw)
In-Reply-To: <YoyjIFI0LTvUHGQr@alley>
Petr Mladek writes:
>PS: I still have to look deeper at the patchset. It might take
> some more days. It seems that nature is not the only one who
> woke up after the winter.
No worries at all! It took me long enough to send it after all :-)
A question for you: I have some minor, non-logic changes ready for v3. Would
you prefer I send v3 for you to review when you get time or leave v2 for you to
review for now? Don't want to interrupt your process if you're part of the way
through doing v2.
Thanks!
Chris
next prev parent reply other threads:[~2022-05-30 10:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 14:24 Chris Down
2022-05-18 14:32 ` Chris Down
2022-05-18 15:34 ` Greg Kroah-Hartman
2022-05-18 19:46 ` Chris Down
2022-05-18 19:54 ` Greg Kroah-Hartman
2022-05-18 20:27 ` Chris Down
2022-05-19 7:04 ` Greg Kroah-Hartman
2022-05-19 14:12 ` Chris Down
2022-05-19 14:35 ` Greg Kroah-Hartman
2022-05-19 15:08 ` Chris Down
2022-05-19 15:24 ` Greg Kroah-Hartman
2022-05-19 15:25 ` Greg Kroah-Hartman
2022-05-19 15:55 ` Chris Down
2022-05-19 17:45 ` Greg Kroah-Hartman
2022-05-19 17:55 ` Chris Down
2022-05-24 9:19 ` Petr Mladek
2022-05-30 10:48 ` Chris Down [this message]
2022-05-30 10:49 ` [OFFLIST] " Chris Down
2022-05-19 7:26 ` Geert Uytterhoeven
2022-05-19 14:37 ` Chris Down
2022-05-19 17:48 ` Geert Uytterhoeven
2022-05-19 18:05 ` Chris Down
2022-05-19 13:59 ` [printk] 6f922c8d53: BUG:kernel_NULL_pointer_dereference,address 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=YpSg5dsQTDX/OsvI@chrisdown.name \
--to=chris@chrisdown.name \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
/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
all inboxes | Powered by JetHome®