[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200624082254.GE8444@alley>
Date: Wed, 24 Jun 2020 10:22:54 +0200
From: Petr Mladek <pmladek@...e.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Herbert Xu <herbert@...dor.apana.org.au>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Andy Shevchenko <andy.shevchenko@...il.com>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
"Steven Rostedt (VMware)" <rostedt@...dmis.org>,
Heiko Carstens <heiko.carstens@...ibm.com>
Subject: Re: linux-next: build failure after merge of the printk tree
On Tue 2020-06-23 17:17:38, Peter Zijlstra wrote:
> On Tue, Jun 23, 2020 at 04:28:58PM +0200, Petr Mladek wrote:
>
> > PS: And yes, it makes sense to push both patches via a single tree to
> > make sure that the lockdep.h split is done first.
>
> That's what I got you tip/locking/header for, pull that topic branch
> into your tree.
I see, I misunderstood it.
I am going to merge the branch once I get the updated 2nd patch.
Best Regards,
Petr
Powered by blists - more mailing lists