From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Mon, 03 Sep 2018 15:45:32 +0200 (CEST) Received: from mail.bootlin.com ([62.4.15.54]:54645 "EHLO mail.bootlin.com" rhost-flags-OK-OK-OK-OK) by eddie.linux-mips.org with ESMTP id S23991344AbeICNp2cLmZP (ORCPT ); Mon, 3 Sep 2018 15:45:28 +0200 Received: by mail.bootlin.com (Postfix, from userid 110) id 9F1DD208A1; Mon, 3 Sep 2018 15:45:23 +0200 (CEST) Received: from localhost (unknown [37.71.171.242]) by mail.bootlin.com (Postfix) with ESMTPSA id 7934220799; Mon, 3 Sep 2018 15:45:23 +0200 (CEST) Date: Mon, 3 Sep 2018 15:45:22 +0200 From: Alexandre Belloni To: Andrew Lunn Cc: Quentin Schulz , ralf@linux-mips.org, paul.burton@mips.com, jhogan@kernel.org, robh+dt@kernel.org, mark.rutland@arm.com, davem@davemloft.net, kishon@ti.com, f.fainelli@gmail.com, allan.nielsen@microchip.com, linux-mips@linux-mips.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, thomas.petazzoni@bootlin.com Subject: Re: [PATCH v2 00/11] mscc: ocelot: add support for SerDes muxing configuration Message-ID: <20180903134522.GC13888@piout.net> References: <20180903093308.24366-1-quentin.schulz@bootlin.com> <20180903133415.GF4445@lunn.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180903133415.GF4445@lunn.ch> User-Agent: Mutt/1.10.1 (2018-07-13) Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 65897 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: alexandre.belloni@bootlin.com Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: linux-mips X-List-ID: linux-mips List-subscribe: List-owner: List-post: List-archive: X-list: linux-mips On 03/09/2018 15:34:15+0200, Andrew Lunn wrote: > > I suggest patches 1 and 8 go through MIPS tree, 2 to 5 and 11 go through > > net while the others (6, 7, 9 and 10) go through the generic PHY subsystem. > > Hi Quentin > > Are you expecting merge conflicts? If not, it might be simpler to gets > ACKs from each maintainer, and then merge it though one tree. > There are some other DT changes for this cycle so those should probably go through MIPS. -- Alexandre Belloni, Bootlin Embedded Linux and Kernel engineering https://bootlin.com