From: Conor Dooley <conor@kernel.org>
To: Javier Carrasco <javier.carrasco.cruz@gmail.com>
Cc: Christian Eggers <ceggers@arri.de>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: iio: light: as73211: add support for as7331
Date: Sat, 23 Dec 2023 12:49:20 +0000 [thread overview]
Message-ID: <20231223-nucleus-taps-7ba9d371c84a@spud> (raw)
In-Reply-To: <20231220-as7331-v1-1-745b73c27703@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 414 bytes --]
On Sat, Dec 23, 2023 at 11:46:13AM +0100, Javier Carrasco wrote:
> This device has the same properties and I2C addresses as the as73211.
> The only difference between them is the photodiodes they use internally,
> which in this case is irrelevant for the bindings.
>
> Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
Cheers,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-12-23 12:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-23 10:46 [PATCH 0/2] iio: light: add support for AMS AS7331 Javier Carrasco
2023-12-23 10:46 ` [PATCH 1/2] dt-bindings: iio: light: as73211: add support for as7331 Javier Carrasco
2023-12-23 12:49 ` Conor Dooley [this message]
2023-12-23 10:46 ` [PATCH 2/2] io: " Javier Carrasco
2023-12-26 16:14 ` Jonathan Cameron
2024-01-02 11:21 ` Javier Carrasco
2024-01-02 19:32 ` Jonathan Cameron
2024-01-01 8:20 ` Christian Eggers
2024-01-02 11:34 ` Javier Carrasco
2023-12-23 12:18 ` [PATCH 0/2] iio: light: add support for AMS AS7331 Christian Eggers
2023-12-23 19:45 ` Javier Carrasco
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=20231223-nucleus-taps-7ba9d371c84a@spud \
--to=conor@kernel.org \
--cc=ceggers@arri.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=javier.carrasco.cruz@gmail.com \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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).