[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200525003706.GA13789@paulmck-ThinkPad-P72>
Date: Sun, 24 May 2020 17:37:06 -0700
From: "Paul E. McKenney" <paulmck@...nel.org>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Borislav Petkov <bp@...en8.de>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Will Deacon <will@...nel.org>, Ingo Molnar <mingo@...e.hu>,
"H. Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
elver@...gle.com
Subject: Re: linux-next: build failure after merge of the tip tree
On Sat, May 23, 2020 at 02:23:45PM -0700, Paul E. McKenney wrote:
> On Sat, May 23, 2020 at 09:05:24PM +0200, Thomas Gleixner wrote:
> > "Paul E. McKenney" <paulmck@...nel.org> writes:
> > > On Sat, May 23, 2020 at 11:54:26AM +0200, Thomas Gleixner wrote:
> > >> core/rcu is the one which diverged and caused the merge conflict with
> > >> PPC to happen twice. So Paul needs to remove the stale core/rcu bits and
> > >> rebase on the current version (which is not going to change again).
> > >
> > > So there will be another noinstr-rcu-* tag, and I will rebase on top
> > > of that, correct? If so, fair enough!
> >
> > Here you go: noinstr-rcu-220-05-23
> >
> > I wanted this to be 2020 and not 220 but I noticed after pushing it
> > out. I guess it still does the job :)
>
> Now -that- is what I call an old-school tag name!!! ;-)
>
> I remerged, rebased, and pushed to -rcu branch "dev".
>
> If it survives testing, I will reset -rcu branch "rcu/next" as well.
And passed! The compile times are back to their old selves on my
laptop as well.
Thank you for setting this up, Thomas!!!
Thanx, Paul
Powered by blists - more mailing lists