From: Petr Mladek <pmladek@suse.com>
To: John Ogness <john.ogness@linutronix.de>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org,
Jason Wessel <jason.wessel@windriver.com>,
Daniel Thompson <daniel.thompson@linaro.org>,
Douglas Anderson <dianders@chromium.org>,
Aaron Tomlin <atomlin@atomlin.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH printk v3 0/7] various cleanups
Date: Tue, 18 Jul 2023 12:44:33 +0200 [thread overview]
Message-ID: <ZLZtEfW1tZOTH53O@alley> (raw)
In-Reply-To: <20230717194607.145135-1-john.ogness@linutronix.de>
On Mon 2023-07-17 21:52:00, John Ogness wrote:
> Hi,
>
> This is v3 of a series providing some cleanup in preparation
> for the threaded/atomic console work. v2 is here [0]. This
> series provides useful cleanups independent of the
> threaded/atomic work.
>
> Changes since v2:
>
> - "NMI safety" patch split into 3 patches: console_unblank,
> keep non-panic CPUs out, do not lock console on panic flush.
>
> - console_unblank() aborts if there are no consoles implementing
> an unblank() callback. This check is performed before taking
> the console lock.
>
> - Commit messages and comments updated to mention the details
> discussed in the v2 feedback.
The patchset looks ready for linux-next. I am going to push it
into printk/linux.git, branch rework/misc-cleanups.
I'll wait a day or two. I think that there is only very small
chance that anyone else would do a review.
Best Regards,
Petr
next prev parent reply other threads:[~2023-07-18 10:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 19:46 John Ogness
2023-07-17 19:46 ` [PATCH printk v3 1/7] kdb: Do not assume write() callback available John Ogness
2023-07-17 19:46 ` [PATCH printk v3 2/7] printk: Reduce console_unblank() usage in unsafe scenarios John Ogness
2023-07-18 3:39 ` Sergey Senozhatsky
2023-07-18 10:21 ` Petr Mladek
2023-07-17 19:46 ` [PATCH printk v3 3/7] printk: Keep non-panic-CPUs out of console lock John Ogness
2023-07-18 3:17 ` Sergey Senozhatsky
2023-07-18 10:23 ` Petr Mladek
2023-07-17 19:46 ` [PATCH printk v3 4/7] printk: Do not take console lock for console_flush_on_panic() John Ogness
2023-07-18 3:18 ` Sergey Senozhatsky
2023-07-18 10:28 ` Petr Mladek
2023-07-17 19:46 ` [PATCH printk v3 5/7] printk: Consolidate console deferred printing John Ogness
2023-07-17 19:46 ` [PATCH printk v3 6/7] printk: Add per-console suspended state John Ogness
2023-07-17 19:46 ` [PATCH printk v3 7/7] printk: Rename abandon_console_lock_in_panic() to other_cpu_in_panic() John Ogness
2023-07-18 10:44 ` Petr Mladek [this message]
2023-07-21 9:17 ` [PATCH printk v3 0/7] various cleanups 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=ZLZtEfW1tZOTH53O@alley \
--to=pmladek@suse.com \
--cc=atomlin@atomlin.com \
--cc=daniel.thompson@linaro.org \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=jason.wessel@windriver.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=tglx@linutronix.de \
/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®