Message ID | 20210303101528.29901-1-john.ogness@linutronix.de (mailing list archive) |
---|---|
Headers | show |
Series | printk: remove logbuf_lock | expand |
Hi John, 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]. Have you got some reply from lkml that it has not delivered there, please? I am not able to get the patchset using b4 tool: $> b4 am -o test 20210303101528.29901-1-john.ogness@linutronix.de Looking up https://lore.kernel.org/r/20210303101528.29901-1-john.ogness%40linutronix.de Grabbing thread from lore.kernel.org/linux-hyperv Analyzing 2 messages in the thread --- Thread incomplete, attempting to backfill Grabbing thread from lore.kernel.org/lkml Server returned an error: 404 Grabbing thread from lore.kernel.org/linux-mtd Server returned an error: 404 Grabbing thread from lore.kernel.org/linuxppc-dev Loaded 2 messages from https://lore.kernel.org/linuxppc-dev/ --- Writing test/v4_20210303_john_ogness_printk_remove_logbuf_lock.mbx ERROR: missing [1/15]! ERROR: missing [2/15]! ERROR: missing [3/15]! ERROR: missing [4/15]! ERROR: missing [5/15]! ERROR: missing [6/15]! ERROR: missing [7/15]! ERROR: missing [8/15]! ERROR: missing [9/15]! ERROR: missing [10/15]! [PATCH next v4 11/15] printk: kmsg_dumper: remove @active field ✓ [PATCH next v4 12/15] printk: introduce a kmsg_dump iterator ERROR: missing [13/15]! [PATCH next v4 14/15] printk: kmsg_dump: remove _nolock() variants ERROR: missing [15/15]! --- Total patches: 3 --- WARNING: Thread incomplete! Cover: test/v4_20210303_john_ogness_printk_remove_logbuf_lock.cover Link: https://lore.kernel.org/r/20210303101528.29901-1-john.ogness@linutronix.de Base: not found git am test/v4_20210303_john_ogness_printk_remove_logbuf_lock.mbx and I do not see it at lore. It has only found copies in linux-hyperv and linux-ppcdev mailing lists, see https://lore.kernel.org/lkml/20210303101528.29901-2-john.ogness@linutronix.de/ Best Regards, Petr
On Wed, 3 Mar 2021 14:18:29 +0100 Petr Mladek <pmladek@suse.com> wrote: > Hi John, > > 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]. > > Have you got some reply from lkml that it has not delivered there, > please? vger has been having some issues as of late, and emails have been coming in slowly. I just received emails I sent more than 24 hours a head of time. Those in charge are trying to work things out. -- Steve
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
On Wed 2021-03-03 16:34:19, Petr Mladek wrote: > 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. The series is committed in printk/linux.git, branch printk-rework. Best Regards, Petr