Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 9 Dec 2020 12:14:57 +0100
From:   Petr Mladek <pmladek@suse.com>
To:     John Ogness <john.ogness@linutronix.de>
Cc:     Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
        Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
        Steven Rostedt <rostedt@goodmis.org>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Thomas Gleixner <tglx@linutronix.de>,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH next v4 0/2] printk: remove logbuf_lock writer-protection
 of ringbuffer
Message-ID: <X9CxsWOCoWPS8KZf@alley>
References: <20201209004453.17720-1-john.ogness@linutronix.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20201209004453.17720-1-john.ogness@linutronix.de>
Precedence: bulk

On Wed 2020-12-09 01:50:51, John Ogness wrote:
> Hello,
> 
> Here is a v4 of the series to partially remove logbuf_lock.
> v3 is here[0]. This series removes logbuf_lock usage of most
> ringbuffer writers. The remaining logbuf_lock users are
> using the lock to synchronize other variables. These other
> users will be addressed in a later series.
> 
> I have tried to keep these changes minimal so that we can feel
> comfortable for the upcoming 5.11 merge window.

Both patches are pushed in printk/linux.git, branch printk-rework.

I hurried so that we could get some testing linux-next before
the merge window opens.

We are going to see if the many barriers in the ring buffer
code are enough ;-) I keep my fingers crossed.

Best Regards,
Petr