From: "Maxime Ripard" <mripard@kernel.org>
To: "Conor Dooley" <conor@kernel.org>
Cc: conor@kernel.org, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
"Conor Dooley" <conor+dt@kernel.org>,
"Conor Dooley" <conor.dooley@microchip.com>,
"Fabio Estevam" <festevam@gmail.com>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Mark Brown" <broonie@kernel.org>,
"Maxime Ripard" <mripard@kernel.org>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Rob Herring" <robh@kernel.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Shawn Guo" <shawnguo@kernel.org>
Subject: Re: [PATCH v1 0/3] Fix incorrect bh2228fv compatible
Date: Wed, 17 Jul 2024 10:23:30 +0000 [thread overview]
Message-ID: <27e6911108d780abc6a7cb688b3229d7@kernel.org> (raw)
In-Reply-To: <20240717-impotence-zippy-254b86593069@spud>
On Wed, 17 Jul 2024 10:59:47 +0100, Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> Maxime made a typo when adding this device to the kernel all the way
> back in 2012, fix the spelling mistake.
>
>
> [ ... ]
Acked-by: Maxime Ripard <mripard@kernel.org>
Thanks!
Maxime
next prev parent reply other threads:[~2024-07-17 10:23 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
2024-07-17 10:23 ` Maxime Ripard [this message]
2024-07-18 16:25 ` (subset) [PATCH v1 0/3] Fix incorrect bh2228fv compatible 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=27e6911108d780abc6a7cb688b3229d7@kernel.org \
--to=mripard@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.