From: Javier Carrasco <javier.carrasco.cruz@gmail.com>
To: 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>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] io: light: as73211: add support for as7331
Date: Tue, 2 Jan 2024 12:34:58 +0100 [thread overview]
Message-ID: <c0c18292-b766-490d-a564-275f25d476cc@gmail.com> (raw)
In-Reply-To: <2337038.ElGaqSPkdT@n95hx1g2>
On 01.01.24 09:20, Christian Eggers wrote:
>
> As I still work with Linux 6.1, I backported this patch for
> that version. A short test with an as73211 didn't show any
> differences.
>
> If I shall test further revisions of this patch, I can do this
> after the 9th of January.
>
>
> If I shall test further revisions of this patch, I can do this
> after the 9th of January.
>
>
> Tested-by: Christian Eggers <ceggers@arri.de>
>
Thanks a lot for testing, I am glad that everything still works as before.
Best regards,
Javier Carrasco
next prev parent reply other threads:[~2024-01-02 11:35 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
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 [this message]
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=c0c18292-b766-490d-a564-275f25d476cc@gmail.com \
--to=javier.carrasco.cruz@gmail.com \
--cc=ceggers@arri.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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).