From: Tony Lindgren <tony@atomide.com>
To: David Miller <davem@davemloft.net>
Cc: devicetree@vger.kernel.org, grygorii.strashko@ti.com,
netdev@vger.kernel.org, nsekhar@ti.com,
linux-kernel@vger.kernel.org, kishon@ti.com, robh+dt@kernel.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 6/6] net: ethernet: ti: cpsw: deprecate cpsw-phy-sel driver
Date: Wed, 20 Feb 2019 13:01:27 -0800 [thread overview]
Message-ID: <20190220210127.GU15711@atomide.com> (raw)
In-Reply-To: <20190220.124155.2226787912266109280.davem@davemloft.net>
* David Miller <davem@davemloft.net> [190220 20:42]:
> From: Tony Lindgren <tony@atomide.com>
> Date: Wed, 20 Feb 2019 12:33:26 -0800
>
> > * David Miller <davem@davemloft.net> [190220 19:23]:
> >> From: Grygorii Strashko <grygorii.strashko@ti.com>
> >> Date: Wed, 20 Feb 2019 17:25:19 +0200
> >>
> >> > Deprecate cpsw-phy-sel driver as it's been replaced with new
> >> > TI phy-gmii-sel PHY driver.
> >> >
> >> > Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
> >>
> >> Acked-by: David S. Miller <davem@davemloft.net>
> >
> > Thanks for the ack, but actually I'd prefer you to pick
> > this patch at some future date. I suggest Grygorii just
> > repost this one after v5.1-rc1.
>
> It's so much easier if you group this with those DT changes, they
> logically belong together as well and it helps someone reading
> the changes in the tree also if they are side by side.
I agree that a group of patches should go together in
most cases.
> Why don't you want to integrate this with them?
Because the arm-soc tree wants dts changes separately in
general. The dts changes are considered firmware describing
hardware. And it makes it possible to split the arm-soc pile
of patches into multiple pull requests. In theory there
should be no dependency between dts changes and driver
changes, but in reality that's not always the case :)
What I can do is set up a separate branch with just this
patch on top of the dts changes that the arm-soc guys can
then merge towards the end of the merge cycle. If that
works for you, let me know and I'll do it.
Regards,
Tony
next prev parent reply other threads:[~2019-02-20 21:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 15:25 [PATCH 0/6] ARM: dts: ti: cpsw: switch to phy-gmii-sel phy driver Grygorii Strashko
2019-02-20 15:25 ` [PATCH 1/6] ARM: dts: dra7: switch to use phy-gmii-sel Grygorii Strashko
2019-02-20 15:25 ` [PATCH 2/6] ARM: dts: dm814x: " Grygorii Strashko
2019-02-20 15:25 ` [PATCH 3/6] ARM: dts: am4372: " Grygorii Strashko
2019-02-20 15:25 ` [PATCH 4/6] ARM: dts: am335x: " Grygorii Strashko
2019-02-20 15:25 ` [PATCH 5/6] dt-bindings: net: ti: deprecate cpsw-phy-sel bindings Grygorii Strashko
2019-02-20 15:25 ` [PATCH 6/6] net: ethernet: ti: cpsw: deprecate cpsw-phy-sel driver Grygorii Strashko
2019-02-20 16:18 ` Tony Lindgren
2019-02-20 19:22 ` David Miller
2019-02-20 20:33 ` Tony Lindgren
2019-02-20 20:41 ` David Miller
2019-02-20 21:01 ` Tony Lindgren [this message]
2019-02-21 0:18 ` David Miller
2019-02-21 16:36 ` Tony Lindgren
2019-02-20 15:48 ` [PATCH 0/6] ARM: dts: ti: cpsw: switch to phy-gmii-sel phy driver Tony Lindgren
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=20190220210127.GU15711@atomide.com \
--to=tony@atomide.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
/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).