From: Rob Herring <robh@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>,
Stephen Boyd <sboyd@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Guenter Roeck <linux@roeck-us.net>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Fix Arm Ltd board node name collisions
Date: Tue, 9 Nov 2021 10:46:48 -0600 [thread overview]
Message-ID: <20211109164650.2233507-1-robh@kernel.org> (raw)
The node name changes in commits 25b892b583cc ("ARM: dts: arm: Update
register-bit-led nodes 'reg' and node names") and 2d3de197a818 ("ARM:
dts: arm: Update ICST clock nodes 'reg' and node names") caused name
collisions with the kernel's handling of ICST clock names and platform
device names. This series fixes the kernel side to handle the DT
changes.
This does break DT ABI compatibility which is partially mitigated if
these changes are backported to stable. The alternative is reverting the
referenced DT changes and coming up with different node names without
unit-addresses. Ultimately, ABI issues are platform maintainers'
decision, not mine.
Rob
Rob Herring (2):
of: Support using 'mask' in making device bus id
clk: versatile: clk-icst: Ensure clock names are unique
drivers/clk/versatile/clk-icst.c | 6 ++++--
drivers/of/platform.c | 10 ++++++++--
2 files changed, 12 insertions(+), 4 deletions(-)
--
2.32.0
next reply other threads:[~2021-11-09 16:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 16:46 Rob Herring [this message]
2021-11-09 16:46 ` [PATCH 1/2] of: Support using 'mask' in making device bus id Rob Herring
2021-11-09 22:20 ` Linus Walleij
2021-11-09 16:46 ` [PATCH 2/2] clk: versatile: clk-icst: Ensure clock names are unique Rob Herring
2021-11-09 22:21 ` Linus Walleij
2021-11-11 0:41 ` Stephen Boyd
2021-11-09 22:22 ` [PATCH 0/2] Fix Arm Ltd board node name collisions Linus Walleij
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=20211109164650.2233507-1-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lorenzo.pieralisi@arm.com \
--cc=sboyd@kernel.org \
--cc=sudeep.holla@arm.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).