Messages in this thread | | | From | Thomas Gleixner <> | Subject | Re: linux-next: build failure after merge of the tip tree | Date | Sat, 23 May 2020 11:54:26 +0200 |
| |
Borislav Petkov <bp@alien8.de> writes:
> On Fri, May 22, 2020 at 05:12:23PM -0700, Paul E. McKenney wrote: >> Marco, Thomas, is there any better setup I can provide Stephen? Or >> is the next-20200519 -rcu tree the best we have right now? > > I've queued the fixes yesterday into tip:locking/kcsan and tglx said > something about you having to rebase anyway. I guess you can find him on > IRC at some point later. :)
locking/kcsan is not the problem (it just has more fixes on top)
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).
Thanks,
tglx
| |