[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20161224214401.521b2182@canb.auug.org.au>
Date: Sat, 24 Dec 2016 21:44:01 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Ingo Molnar <mingo@...nel.org>
Cc: James Bottomley <James.Bottomley@...senPartnership.com>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Manish Rangankar <manish.rangankar@...ium.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Nilesh Javali <nilesh.javali@...ium.com>,
Adheer Chandravanshi <adheer.chandravanshi@...gic.com>,
Chad Dupuis <chad.dupuis@...ium.com>,
Saurav Kashyap <saurav.kashyap@...ium.com>,
Arun Easi <arun.easi@...ium.com>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Subject: Re: linux-next: build failure after merge of the scsi tree
Hi Ingo,
On Sat, 24 Dec 2016 11:15:08 +0100 Ingo Molnar <mingo@...nel.org> wrote:
>
> Yeah, we'll handle it - that's why the final chunk of changes were left to after
> -rc1, to not cause such merge conflicts upstream.
Excellent, thanks.
> For now I've excluded the relevant -tip side commits from the linux-next branch.
Well, there probably won't be any linux-next releases until Jan 3, so that's ok.
--
Cheers,
Stephen Rothwell
Powered by blists - more mailing lists