[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87lefmq0yk.fsf@jogness.linutronix.de>
Date: Tue, 11 Jul 2023 11:04:11 +0206
From: John Ogness <john.ogness@...utronix.de>
To: Daniel Thompson <daniel.thompson@...aro.org>
Cc: Petr Mladek <pmladek@...e.com>,
Sergey Senozhatsky <senozhatsky@...omium.org>,
Steven Rostedt <rostedt@...dmis.org>,
Thomas Gleixner <tglx@...utronix.de>,
linux-kernel@...r.kernel.org,
Jason Wessel <jason.wessel@...driver.com>,
Douglas Anderson <dianders@...omium.org>,
Aaron Tomlin <atomlin@...mlin.com>,
kgdb-bugreport@...ts.sourceforge.net
Subject: Re: [PATCH printk v2 1/5] kdb: do not assume write() callback
available
On 2023-07-11, Daniel Thompson <daniel.thompson@...aro.org> wrote:
> For v1 I shared an ack rather than queuing the patch. Although reading
> the thread back it is possible that was based on a misunderstanding
> (https://lore.kernel.org/lkml/20230309113020.GA78621@aspen.lan/ ).
>
> Anyhow, it looks like you have designed the new series to be picked
> individually?
I understood that Petr will carry the patch. Yes, this series only
includes the non-atomic/non-threaded cleanups so that it will be easier
for Petr to send the full series off to linux-next.
For this patch there is nothing left to do. I should have removed the
kdb people/lists from the mailing. Sorry about that.
John Ogness
Powered by blists - more mailing lists