[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210617212829.33032350@elm.ozlabs.ibm.com>
Date: Thu, 17 Jun 2021 21:28:29 +1000
From: Stephen Rothwell <sfr@...hwell.id.au>
To: Petr Mladek <pmladek@...e.com>
Cc: John Ogness <john.ogness@...utronix.de>,
Sergey Senozhatsky <senozhatsky@...omium.org>,
Steven Rostedt <rostedt@...dmis.org>,
Thomas Gleixner <tglx@...utronix.de>,
linux-kernel@...r.kernel.org,
Stephen Rothwell <sfr@...b.auug.org.au>,
Andrew Morton <akpm@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>,
Daniel Bristot de Oliveira <bristot@...hat.com>,
Stephen Boyd <swboyd@...omium.org>,
Alexander Potapenko <glider@...gle.com>,
"Paul E. McKenney" <paulmck@...nel.org>
Subject: Re: [PATCH next v4 0/2] introduce printk cpu lock
Hi all,
On Thu, 17 Jun 2021 13:23:20 +0200 Petr Mladek <pmladek@...e.com> wrote:
>
> On Thu 2021-06-17 11:56:49, John Ogness wrote:
> >
> > This series is against next-20210616.
>
> The patchset is ready for linux-next from my POV. We are getting close
> to the merge window so I am going to push it tomorrow. We could always
> remove it when anyone has comments the following week.
Unless this patch series is going to be part of Andrew Morton's
post-next patch series, it must not be based on the whole of linux-next.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists