From: Jonathan Cameron <jic23@kernel.org>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: "Frank Li" <Frank.Li@nxp.com>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
"Nuno Sá" <nuno.sa@analog.com>,
linux-iio@vger.kernel.org, "Andy Shevchenko" <andy@kernel.org>,
"Gregory Clement" <gregory.clement@bootlin.com>,
linux-kernel@vger.kernel.org,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Conor Dooley" <conor+dt@kernel.org>
Subject: Re: [PATCH 1/1] dt-bindings: iio: adc: nxp,lpc3220-adc: allow clocks property
Date: Sat, 28 Jun 2025 16:33:13 +0100 [thread overview]
Message-ID: <20250628163313.187d4a3e@jic23-huawei> (raw)
In-Reply-To: <175105627901.33520.13967663171471942396.robh@kernel.org>
On Fri, 27 Jun 2025 15:31:19 -0500
"Rob Herring (Arm)" <robh@kernel.org> wrote:
> On Tue, 24 Jun 2025 16:13:02 -0400, Frank Li wrote:
> > Allow clocks property to fix below CHECK_DTB warning:
> > arch/arm/boot/dts/nxp/lpc/lpc3250-ea3250.dtb: adc@40048000 (nxp,lpc3220-adc): 'clocks' does not match any of the regexes: 'pinctrl-[0-9]+'
> >
> > Signed-off-by: Frank Li <Frank.Li@nxp.com>
> > ---
> > Documentation/devicetree/bindings/iio/adc/nxp,lpc3220-adc.yaml | 3 +++
> > 1 file changed, 3 insertions(+)
> >
>
> Acked-by: Rob Herring (Arm) <robh@kernel.org>
>
I was in two minds on this one wrt to whether to pick it up as a fix.
It's clearly been broken a long time though so I'm not going to rush it in.
Let me know if you think I should!
Applied to the togreg branch of iio.git and pushed out as testing because
other stuff I queued today will benefit from a 0-day pass before I expose
it to linux-next.
Thanks,
Jonathan
prev parent reply other threads:[~2025-06-28 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 20:13 [PATCH 1/1] dt-bindings: iio: adc: nxp,lpc3220-adc: allow clocks property Frank Li
2025-06-27 20:31 ` Rob Herring (Arm)
2025-06-28 15:33 ` Jonathan Cameron [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=20250628163313.187d4a3e@jic23-huawei \
--to=jic23@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=gregory.clement@bootlin.com \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.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).