From: Krzysztof Kozlowski <krzk@kernel.org>
To: Alexandru Gagniuc <mr.nuke.me@gmail.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: ipq9574: Use 'usb-phy' for node names
Date: Tue, 9 Dec 2025 22:47:59 +0100 [thread overview]
Message-ID: <8fb5dc02-080c-4c99-941c-69f3ec346597@kernel.org> (raw)
In-Reply-To: <20251209160755.3878878-1-mr.nuke.me@gmail.com>
On 09/12/2025 17:07, Alexandru Gagniuc wrote:
> The devicetree spec allows node names of "usb-phy". So be more
> specific for the USB PHYs, and name the nodes "usb-phy" instead of
> just "phy".
>
> Signed-off-by: Alexandru Gagniuc <mr.nuke.me@gmail.com>
> ---
> arch/arm64/boot/dts/qcom/ipq9574.dtsi | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/qcom/ipq9574.dtsi b/arch/arm64/boot/dts/qcom/ipq9574.dtsi
> index 86c9cb9fffc98..4b8cbf1ff131b 100644
> --- a/arch/arm64/boot/dts/qcom/ipq9574.dtsi
> +++ b/arch/arm64/boot/dts/qcom/ipq9574.dtsi
> @@ -702,7 +702,7 @@ qpic_nand: spi@79b0000 {
> status = "disabled";
> };
>
> - usb_0_qusbphy: phy@7b000 {
> + usb_0_qusbphy: usb-phy@7b000 {
Huh? Why changing perfectly correct name? That's just churn.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-12-09 21:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 16:07 [PATCH] arm64: dts: qcom: ipq9574: Use 'usb-phy' for node names Alexandru Gagniuc
2025-12-09 16:17 ` Dmitry Baryshkov
2025-12-09 16:26 ` mr.nuke.me
2025-12-09 21:48 ` Krzysztof Kozlowski
2025-12-09 21:59 ` mr.nuke.me
2025-12-10 6:03 ` Krzysztof Kozlowski
2025-12-10 16:44 ` mr.nuke.me
2025-12-09 21:47 ` Krzysztof Kozlowski [this message]
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=8fb5dc02-080c-4c99-941c-69f3ec346597@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mr.nuke.me@gmail.com \
--cc=robh@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).