From: Krzysztof Kozlowski <krzk@kernel.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-arm-kernel@lists.infradead.org
Cc: Alexey Charkov <alchark@gmail.com>, Andrew Lunn <andrew@lunn.ch>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org,
Gregory Clement <gregory.clement@bootlin.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-omap@vger.kernel.org,
Piotr Wojtaszczyk <piotr.wojtaszczyk@timesys.com>,
Rob Herring <robh@kernel.org>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Shiraz Hashim <shiraz.linux.kernel@gmail.com>,
soc@lists.linux.dev, Tony Lindgren <tony@atomide.com>,
Viresh Kumar <vireshk@kernel.org>,
Vladimir Zapolskiy <vz@mleia.com>
Subject: Re: [PATCH 0/5] ARM: dts: fix faulty ohci/ehci node names
Date: Sun, 30 Mar 2025 17:57:21 +0200 [thread overview]
Message-ID: <2d2307d9-6a5a-400c-b209-ae2b31ef87b6@kernel.org> (raw)
In-Reply-To: <20250330121326.9069-7-wsa+renesas@sang-engineering.com>
On 30/03/2025 14:13, Wolfram Sang wrote:
> After I fixed this for the at91-boards I was interested in, I let the
> scripts run for the other boards, too, of course. Here is the outcome.
> 49 less dtbs_check errors. Build bots were happy. No dependencies, I
> suggest sub-trees apply them on their own. Thanks!
>
For this and the rest patches, I would not call it "fix" in the subject
because there is no bug to fix here and you just might confuse AUTOSEL.
What's more backporting this might actually cause regressions, because
in rare cases node name is an ABI. Therefore avoid calling anything here
fix.
You just adjust or align them with coding style or what
bindings/dtschema expect (but it expects due to generic naming
convention which is still just convention).
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-30 15:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-30 12:13 [PATCH 0/5] ARM: dts: fix faulty ohci/ehci node names Wolfram Sang
2025-03-30 12:13 ` [PATCH 1/5] ARM: dts: marvell: " Wolfram Sang
2025-03-30 12:13 ` [PATCH 2/5] ARM: dts: nxp: lpc: " Wolfram Sang
2025-03-30 12:13 ` [PATCH 3/5] ARM: dts: st: " Wolfram Sang
2025-03-30 12:13 ` [PATCH 4/5] ARM: dts: ti: omap: " Wolfram Sang
2025-03-30 12:13 ` [PATCH 5/5] ARM: dts: vt8500: " Wolfram Sang
2025-03-30 15:57 ` Krzysztof Kozlowski [this message]
2025-03-30 15:59 ` [PATCH 0/5] ARM: dts: " Krzysztof Kozlowski
2025-03-30 16:38 ` Wolfram Sang
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=2d2307d9-6a5a-400c-b209-ae2b31ef87b6@kernel.org \
--to=krzk@kernel.org \
--cc=alchark@gmail.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=piotr.wojtaszczyk@timesys.com \
--cc=robh@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=shiraz.linux.kernel@gmail.com \
--cc=soc@lists.linux.dev \
--cc=tony@atomide.com \
--cc=vireshk@kernel.org \
--cc=vz@mleia.com \
--cc=wsa+renesas@sang-engineering.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