From: Krzysztof Kozlowski <krzk@kernel.org>
To: Conor Dooley <conor@kernel.org>, linux-kernel@vger.kernel.org
Cc: Conor Dooley <conor.dooley@microchip.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Mark Brown <broonie@kernel.org>,
Maxime Ripard <mripard@kernel.org>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, linux-spi@vger.kernel.org
Subject: Re: [PATCH v1 3/3] ARM: dts: nxp: correct DAC compatible on Crystalfontz's CFA10049
Date: Sat, 20 Jul 2024 20:26:09 +0200 [thread overview]
Message-ID: <2599a8a5-1bbc-41a7-9842-57caec3a3815@kernel.org> (raw)
In-Reply-To: <20240717-ruse-cardinal-c30cf11bbf1e@spud>
On 17/07/2024 11:59, Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> When Maxime originally added the BH2228FV to the kernel, he spelt it
> incorrectly - the d should have been a b. Correct the compatible used in
> the devicetree.
>
> Fixes: db7a8946dc40 ("ARM: dts: cfa10049: Add the DH2228FV DAC to the DTS")
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
> ---
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-07-20 18:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 9:59 [PATCH v1 0/3] Fix incorrect bh2228fv compatible Conor Dooley
2024-07-17 9:59 ` [PATCH v1 1/3] dt-bindings: trivial-devices: fix Rohm BH2228FV compatible string Conor Dooley
2024-07-17 9:59 ` [PATCH v1 2/3] spi: spidev: add correct compatible for Rohm BH2228FV Conor Dooley
2024-07-17 9:59 ` [PATCH v1 3/3] ARM: dts: nxp: correct DAC compatible on Crystalfontz's CFA10049 Conor Dooley
2024-07-20 18:26 ` Krzysztof Kozlowski [this message]
2024-07-17 10:23 ` [PATCH v1 0/3] Fix incorrect bh2228fv compatible Maxime Ripard
2024-07-18 16:25 ` (subset) " Mark Brown
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=2599a8a5-1bbc-41a7-9842-57caec3a3815@kernel.org \
--to=krzk@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).