From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: David Miller <davem@davemloft.net>
Cc: andrew@lunn.ch, quentin.schulz@bootlin.com, ralf@linux-mips.org,
paul.burton@mips.com, jhogan@kernel.org, robh+dt@kernel.org,
mark.rutland@arm.com, 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
Date: Tue, 4 Sep 2018 17:16:53 +0200 [thread overview]
Message-ID: <20180904151653.GI13888@piout.net> (raw)
In-Reply-To: <20180903.220910.899357653888940454.davem@davemloft.net>
On 03/09/2018 22:09:10-0700, David Miller wrote:
> From: Alexandre Belloni <alexandre.belloni@bootlin.com>
> Date: Mon, 3 Sep 2018 15:45:22 +0200
>
> > 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.
>
> No objection for this going through the MIPS tree, and from me:
>
What I meant was that 1/11 and 8/11 should go through MIPS because of
the potential conflicts. The other patches can go through net-next as
that will make more sense. Maybe Quentin can split the series in two,
one for MIPS and one for net if that makes it easier for you to apply.
> Acked-by: David S. Miller <davem@davemloft.net>
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-09-04 15:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 9:32 [PATCH v2 00/11] mscc: ocelot: add support for SerDes muxing configuration Quentin Schulz
2018-09-03 9:32 ` [PATCH v2 01/11] MIPS: mscc: ocelot: make HSIO registers address range a syscon Quentin Schulz
2018-09-03 9:32 ` [PATCH net-next v2 02/11] dt-bindings: net: ocelot: remove hsio from the list of register address spaces Quentin Schulz
2018-09-03 9:33 ` [PATCH net-next v2 03/11] net: mscc: ocelot: get HSIO regmap from syscon Quentin Schulz
2018-09-03 9:33 ` [PATCH net-next v2 04/11] net: mscc: ocelot: move the HSIO header to include/soc Quentin Schulz
2018-09-03 9:33 ` [PATCH net-next v2 05/11] net: mscc: ocelot: simplify register access for PLL5 configuration Quentin Schulz
2018-09-03 9:33 ` [PATCH v2 06/11] phy: add QSGMII and PCIE modes Quentin Schulz
2018-09-03 9:33 ` [PATCH v2 07/11] dt-bindings: phy: add DT binding for Microsemi Ocelot SerDes muxing Quentin Schulz
2018-09-03 9:33 ` [PATCH v2 08/11] MIPS: mscc: ocelot: add SerDes mux DT node Quentin Schulz
2018-09-03 9:33 ` [PATCH v2 09/11] dt-bindings: add constants for Microsemi Ocelot SerDes driver Quentin Schulz
2018-09-03 9:33 ` [PATCH v2 10/11] phy: add driver for Microsemi Ocelot SerDes muxing Quentin Schulz
2018-09-03 9:33 ` [PATCH net-next v2 11/11] net: mscc: ocelot: make use of SerDes PHYs for handling their configuration Quentin Schulz
2018-09-03 13:34 ` [PATCH v2 00/11] mscc: ocelot: add support for SerDes muxing configuration Andrew Lunn
2018-09-03 13:45 ` Alexandre Belloni
2018-09-04 5:09 ` David Miller
2018-09-04 15:16 ` Alexandre Belloni [this message]
2018-09-04 16:10 ` Paul Burton
2018-09-04 18:00 ` Quentin Schulz
2018-09-04 23:03 ` Paul Burton
2018-09-05 9:07 ` Alexandre Belloni
2018-09-04 17:17 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180904151653.GI13888@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=allan.nielsen@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jhogan@kernel.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=paul.burton@mips.com \
--cc=quentin.schulz@bootlin.com \
--cc=ralf@linux-mips.org \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).