From: David Miller <davem@davemloft.net>
To: ioana.ciornei@nxp.com
Cc: netdev@vger.kernel.org, shawnguo@kernel.org, robh+dt@kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH net-next v2 00/10] arm64: dts: layerscape: update MAC nodes with PHY information
Date: Fri, 02 Oct 2020 16:13:18 -0700 (PDT) [thread overview]
Message-ID: <20201002.161318.726844448692603677.davem@davemloft.net> (raw)
In-Reply-To: <20201002210737.27645-1-ioana.ciornei@nxp.com>
From: Ioana Ciornei <ioana.ciornei@nxp.com>
Date: Sat, 3 Oct 2020 00:07:27 +0300
> This patch set aims to add the necessary DTS nodes to complete the
> MAC/PCS/PHY representation on DPAA2 devices. The external MDIO bus nodes
> and the PHYs found on them are added, along with the PCS MDIO internal
> buses and their PCS PHYs. Also, links to these PHYs are added from the
> DPMAC node.
>
> I am resending these via netdev because I am not really sure if Shawn is
> still able to take them in time for 5.10 since his last activity on the
> tree has been some time ago.
> I tested them on linux-next and there are no conflicts.
>
> Changes in v2:
> - documented the dpmac node into a new yaml entry
> - dropped the '0x' from some unit addresses
I don't feel comfortable taking such a sizable set of DT changes into
the networking tree rather than the devicetree or ARM tree(s).
I know we're fast and more responsive than the other subsystems (by
several orders of magnitude) but that isn't a reason to bypass the
correct tree for these changes.
Thank you.
next prev parent reply other threads:[~2020-10-02 23:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 21:07 [PATCH net-next v2 00/10] arm64: dts: layerscape: update MAC nodes with PHY information Ioana Ciornei
2020-10-02 21:07 ` [PATCH net-next v2 01/10] dt-bindings: net: add the dpaa2-mac DTS definition Ioana Ciornei
2020-10-06 20:56 ` Rob Herring
2020-10-07 10:51 ` Ioana Ciornei
2020-10-02 21:07 ` [PATCH net-next v2 02/10] arm64: dts: ls1088a: add external MDIO device nodes Ioana Ciornei
2020-10-02 21:07 ` [PATCH net-next v2 03/10] arm64: dts: ls1088ardb: add QSGMII PHY nodes Ioana Ciornei
2020-10-02 21:07 ` [PATCH net-next v2 04/10] arm64: dts: ls1088ardb: add necessary DTS nodes for DPMAC2 Ioana Ciornei
2020-10-02 21:07 ` [PATCH net-next v2 05/10] arm64: dts: ls208xa: add the external MDIO nodes Ioana Ciornei
2020-10-02 21:07 ` [PATCH net-next v2 06/10] arm64: dts: ls2088ardb: add PHY nodes for the CS4340 PHYs Ioana Ciornei
2020-10-02 21:07 ` [PATCH net-next v2 07/10] arm64: dts: ls2088ardb: add PHY nodes for the AQR405 PHYs Ioana Ciornei
2020-10-02 21:07 ` [PATCH net-next v2 08/10] arm64: dts: ls208xa: add PCS MDIO and PCS PHY nodes Ioana Ciornei
2020-10-02 21:07 ` [PATCH net-next v2 09/10] arm64: dts: lx2160a: " Ioana Ciornei
2020-10-02 21:07 ` [PATCH net-next v2 10/10] arm64: dts: lx2160ardb: add nodes for the AQR107 PHYs Ioana Ciornei
2020-10-02 23:13 ` David Miller [this message]
2020-10-03 4:35 ` [PATCH net-next v2 00/10] arm64: dts: layerscape: update MAC nodes with PHY information Ioana Ciornei
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=20201002.161318.726844448692603677.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=ioana.ciornei@nxp.com \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=shawnguo@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).