[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171009195634.gzxwcqn7xklumqyr@sirena.co.uk>
Date: Mon, 9 Oct 2017 20:56:34 +0100
From: Mark Brown <broonie@...nel.org>
To: Mika Westerberg <mika.westerberg@...ux.intel.com>
Cc: Darren Hart <dvhart@...radead.org>,
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 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.
I guess that's something best sorted out either in the relevant trees or
during the merge window?
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists