[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200625071959.GA18744@dhcp-128-65.nay.redhat.com>
Date: Thu, 25 Jun 2020 15:19:59 +0800
From: Dave Young <dyoung@...hat.com>
To: John Ogness <john.ogness@...utronix.de>
Cc: Petr Mladek <pmladek@...e.com>,
Andrea Parri <parri.andrea@...il.com>,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
Paul McKenney <paulmck@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
kexec@...ts.infradead.org, linux-kernel@...r.kernel.org,
Steven Rostedt <rostedt@...dmis.org>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH v3 0/3] printk: replace ringbuffer
Hi John,
On 06/18/20 at 04:55pm, John Ogness wrote:
> Hello,
>
> Here is a v3 for the first series to rework the printk
> subsystem. The v2 and history are here [0]. This first series
> only replaces the existing ringbuffer implementation. No locking
> is removed. No semantics/behavior of printk are changed.
>
> Reviews on the ringbuffer are still ongoing, but I was asked to
> post this new version since several changes from v2 have been
> already agreed upon.
>
> The series is based on v5.8-rc1.
Do you have the kdump userspace part link so that people can try
and do some testing?
Eg. some makedumpfile/crash tool git branch etc.
Thanks
Dave
Powered by blists - more mailing lists