[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87y0oiylrb.fsf@jogness.linutronix.de>
Date: Fri, 07 Nov 2025 15:18:40 +0106
From: John Ogness <john.ogness@...utronix.de>
To: Petr Mladek <pmladek@...e.com>, Breno Leitao <leitao@...ian.org>
Cc: Sergey Senozhatsky <senozhatsky@...omium.org>, Steven Rostedt
<rostedt@...dmis.org>, Mike Galbraith <efault@....de>,
linux-kernel@...r.kernel.org, Greg Kroah-Hartman
<gregkh@...uxfoundation.org>
Subject: Re: [PATCH printk v2 1/1] printk: nbcon: Allow unsafe
write_atomic() for panic
On 2025-11-07, Petr Mladek <pmladek@...e.com> wrote:
>> I would prefer you do it through the printk tree for 6.19 and I use it
>> in the next releae (6.20).
>
> OK, I have just committed the patch into printk/linux.git,
> branch rework/write_atomic-unsafe. It is intended for 6.19 merge window.
Thanks for fixing it up the patch for the kdb series.
John
Powered by blists - more mailing lists