[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171009231810.GI12321@fury>
Date: Mon, 9 Oct 2017 16:18:10 -0700
From: Darren Hart <dvhart@...radead.org>
To: Mark Brown <broonie@...nel.org>
Cc: Mika Westerberg <mika.westerberg@...ux.intel.com>,
Mario Limonciello <mario.limonciello@...l.com>,
Yehezkel Bernat <yehezkel.bernat@...el.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Amir Levy <amir.jer.levy@...el.com>,
Michael Jamet <michael.jamet@...el.com>,
"David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org,
Linux-Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: manual merge of the drivers-x86 tree with the
net-next tree
On Mon, Oct 09, 2017 at 08:56:34PM +0100, Mark Brown wrote:
> On Mon, Oct 09, 2017 at 10:43:01PM +0300, Mika Westerberg wrote:
>
> > If possible, I would rather move this chapter to be before "Networking
> > over Thunderbolt cable". Reason is that it then follows NVM flashing
> > chapter which is typically where you need to force power in the first
> > place.
>
Agreed.
> I guess that's something best sorted out either in the relevant trees or
> during the merge window?
I'm not sure how we would deal with it in the trees. Best to note this during
the merge window - whichever goes in second. Test merge will identify the merge
conflict, and we can include a note to Linus on the preference.
--
Darren Hart
VMware Open Source Technology Center
Powered by blists - more mailing lists