[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180502.110617.304411895589508709.davem@davemloft.net>
Date: Wed, 02 May 2018 11:06:17 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: wens@...e.org
Cc: maxime.ripard@...tlin.com, mturquette@...libre.com,
sboyd@...nel.org, peppe.cavallaro@...com, robh+dt@...nel.org,
mark.rutland@....com, broonie@...nel.org,
linux-arm-kernel@...ts.infradead.org, linux-clk@...r.kernel.org,
devicetree@...r.kernel.org, netdev@...r.kernel.org,
clabbe.montjoie@...il.com, icenowy@...c.io
Subject: Re: [PATCH net-next v2 00/15] ARM: sun8i: r40: Add Ethernet support
From: Chen-Yu Tsai <wens@...e.org>
Date: Wed, 2 May 2018 00:33:45 +0800
> I should've mentioned that patches 3 ~ 10, and only these, should go
> through net-next. sunxi will handle the remaining clk, device tree, and
> soc driver patches.
Ok, I just noticed this.
Why don't you just post those patches separately as a series on their
own then, in order to avoid confusion?
Then you can adjust the patch series header posting to explain the
non-net-next changes, where they got merged, and what they provide
in order to faciliate the net-next changes.
Thanks.
Powered by blists - more mailing lists