[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170811234920.794b5647@canb.auug.org.au>
Date: Fri, 11 Aug 2017 23:49:20 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Ingo Molnar <mingo@...nel.org>
Cc: Peter Zijlstra <peterz@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
Linux-Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Nadav Amit <namit@...are.com>,
Linus <torvalds@...ux-foundation.org>
Subject: Re: linux-next: manual merge of the akpm-current tree with the tip
tree
Hi Ingo,
On Fri, 11 Aug 2017 14:44:25 +0200 Ingo Molnar <mingo@...nel.org> wrote:
>
> * Peter Zijlstra <peterz@...radead.org> wrote:
>
> > On Fri, Aug 11, 2017 at 01:56:07PM +0200, Ingo Molnar wrote:
> > > I've done a minimal conflict resolution merge locally. Peter, could you please
> > > double check my resolution, in:
> > >
> > > 040cca3ab2f6: Merge branch 'linus' into locking/core, to resolve conflicts
> >
> > That merge is a bit wonky, but not terminally broken afaict.
> >
> > It now does two TLB flushes, the below cleans that up.
>
> Cool, thanks - I've applied it as a separate commit, to reduce the evilness of the
> merge commit.
>
> Will push it all out in time to make Stephen's Monday morning a bit less of a
> Monday morning.
Thanks you very much.
--
Cheers,
Stephen Rothwell
Powered by blists - more mailing lists