From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Tim Harvey <tharvey@gateworks.com>
Cc: Andrew Lunn <andrew@lunn.ch>, Fabio Estevam <festevam@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] ARM: dts: imx6qdl-gw5904: add internal mdio nodes
Date: Mon, 5 Dec 2022 21:15:09 +0200 [thread overview]
Message-ID: <20221205191509.moan3imfllfpxkb7@skbuf> (raw)
In-Reply-To: <CAJ+vNU1M-LEiM2guowP-Ubb8cFnQE+YCFTZ=vL2C79Y0g0v1dQ@mail.gmail.com>
On Mon, Dec 05, 2022 at 11:10:45AM -0800, Tim Harvey wrote:
> before adding the internal PHY nodes it works fine so no backporting
> needed. I just don't want to add the complete/unambiguous dt-bindings
> until your patch lands as at that point it would otherwise be broken.
Right, but there is some debate on whether device tree updates should
require new kernel or not. Since in this case, kernels 5.18 and newer
can trivially support the updated device trees with this change, I think
it would be silly not to let it be backported. As for older kernels, it
really depends on what the board ships with.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-12-05 19:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 0:31 [PATCH 1/2] ARM: dts: imx6qdl-gw5904: add internal mdio nodes Tim Harvey
2022-12-01 0:31 ` [PATCH 2/2] ARM: dts: imx6qdl-gw5904: add dt props for populating eth MAC addrs Tim Harvey
2022-12-02 1:02 ` Fabio Estevam
2022-12-02 1:02 ` [PATCH 1/2] ARM: dts: imx6qdl-gw5904: add internal mdio nodes Fabio Estevam
2022-12-02 13:08 ` Andrew Lunn
2022-12-02 16:48 ` Tim Harvey
2022-12-02 17:30 ` Andrew Lunn
2022-12-02 22:29 ` Tim Harvey
2022-12-04 0:15 ` Andrew Lunn
2022-12-05 17:10 ` Vladimir Oltean
2022-12-05 18:01 ` Tim Harvey
2022-12-05 19:02 ` Vladimir Oltean
2022-12-05 19:10 ` Tim Harvey
2022-12-05 19:15 ` Vladimir Oltean [this message]
2022-12-05 19:24 ` Tim Harvey
2022-12-05 19:37 ` Vladimir Oltean
2022-12-05 17:27 ` Vladimir Oltean
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=20221205191509.moan3imfllfpxkb7@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=tharvey@gateworks.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).