From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: linux-next: manual merge of the drivers-x86 tree with the
 net-next tree
Date: Tue, 10 Oct 2017 14:49:20 +0300
Message-ID: <20171010114920.GY2761@lahna.fi.intel.com>
References: <20171009175633.dm7hjmgoxusspue5@sirena.co.uk>
 <20171009194301.GP2761@lahna.fi.intel.com>
 <20171009195634.gzxwcqn7xklumqyr@sirena.co.uk>
 <20171009231810.GI12321@fury>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Mark Brown <broonie@kernel.org>,
        Mario Limonciello <mario.limonciello@dell.com>,
        Yehezkel Bernat <yehezkel.bernat@intel.com>,
        Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
        Amir Levy <amir.jer.levy@intel.com>,
        Michael Jamet <michael.jamet@intel.com>,
        "David S. Miller" <davem@davemloft.net>, netdev@vger.kernel.org,
        Linux-Next Mailing List <linux-next@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
To: Darren Hart <dvhart@infradead.org>
Return-path: <linux-kernel-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <20171009231810.GI12321@fury>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: netdev.vger.kernel.org

On Mon, Oct 09, 2017 at 04:18:10PM -0700, Darren Hart wrote:

> 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.

That sounds good, thanks!