[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180208070350.mxirhg32zljp2e4k@gmail.com>
Date: Thu, 8 Feb 2018 08:03:50 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Will Deacon <will.deacon@....com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Thomas Gleixner <tglx@...utronix.de>,
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 <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: manual merge of the tip tree with Linus' tree
* Will Deacon <will.deacon@....com> wrote:
> For the sake of avoiding the conflict, can we just drop it for now, please?
Yeah, so I resolved the conflict by merging the (already upstream) bits and Linus
pulled that resolution. From now on the level of comments you want there is up to
you! :-)
Thanks,
Ingo
Powered by blists - more mailing lists