[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <yq1wp1yw8ew.fsf@oracle.com>
Date: Thu, 07 Dec 2017 16:11:03 -0500
From: "Martin K. Petersen" <martin.petersen@...cle.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Bart Van Assche <Bart.VanAssche@....com>,
"josh\@joshtriplett.org" <josh@...htriplett.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-scsi\@vger.kernel.org" <linux-scsi@...r.kernel.org>,
"linux-next\@vger.kernel.org" <linux-next@...r.kernel.org>,
"martin.petersen\@oracle.com" <martin.petersen@...cle.com>,
"ptikhomirov\@virtuozzo.com" <ptikhomirov@...tuozzo.com>
Subject: Re: linux-next: build failure after merge of the scsi-mkp tree
Stephen,
>> I have to defer to you guys on that one. Left to myself, I will just
>> push it into the next merge window (as opposed to using my normal
>> process, which at this point would get it into the one following).
>>
>> So please let me know how you would like to proceed.
>
> Clearly, it needs to go via Martin's tree as otherwise his tree will
> not build in some circumstances ... or if it going to cause problems
> for Paul, then it should be in a separate non-rebasing branch (probably
> of Paul's tree) that is merged into Pauls main branch and Marin's tree.
I'm perfectly OK with taking it through the SCSI tree. Probably the path
of least resistance.
--
Martin K. Petersen Oracle Linux Engineering
Powered by blists - more mailing lists