[PATCH next v4 00/15] printk: remove logbuf_lock · John Ogness <john.ogness@linutronix.de> · 2021-03-03
[PATCH next v4 14/15] printk: kmsg_dump: remove _nolock() variants · John Ogness <john.ogness@linutronix.de> · 2021-03-03
[PATCH next v4 11/15] printk: kmsg_dumper: remove @active field · John Ogness <john.ogness@linutronix.de> · 2021-03-03
[PATCH next v4 12/15] printk: introduce a kmsg_dump iterator · John Ogness <john.ogness@linutronix.de> · 2021-03-03
Re: [PATCH next v4 12/15] printk: introduce a kmsg_dump iterator · Petr Mladek <pmladek@suse.com> · 2021-03-03
lkml delivery: was: Re: [PATCH next v4 00/15] printk: remove logbuf_lock · Petr Mladek <pmladek@suse.com> · 2021-03-03
Re: lkml delivery: was: Re: [PATCH next v4 00/15] printk: remove logbuf_lock · Steven Rostedt <rostedt@goodmis.org> · 2021-03-03
Re: [PATCH next v4 00/15] printk: remove logbuf_lock · Petr Mladek <pmladek@suse.com> · 2021-03-03
Re: [PATCH next v4 00/15] printk: remove logbuf_lock · Petr Mladek <pmladek@suse.com> · 2021-03-08

Re: [PATCH next v4 00/15] printk: remove logbuf_lock

From: Petr Mladek <pmladek@suse.com>
Date: 2021-03-03 18:52:53
Also in: linux-hyperv, linux-um, lkml

On Wed 2021-03-03 11:15:13, John Ogness wrote:

Hello,

Here is v4 of a series to remove @logbuf_lock, exposing the
ringbuffer locklessly to both readers and writers. v3 is
here [0].

The series look ready. I am going to push it into printk/linux.git
the following week unless anyone speaks against it in the meantime.

Best Regards,
Petr

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help