From: Javier Carrasco <javier.carrasco.cruz@gmail.com>
To: Christian Eggers <ceggers@gmx.de>,
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 0/2] iio: light: add support for AMS AS7331
Date: Sat, 23 Dec 2023 20:45:52 +0100 [thread overview]
Message-ID: <acb74002-31ee-4130-96e1-9ac497a15c2e@gmail.com> (raw)
In-Reply-To: <5750063.DvuYhMxLoT@zbook-studio-g3>
Hi Christian,
On 23.12.23 13:18, Christian Eggers wrote:> I still use the original
AS73211, so I can offer testing with it. I am
> currently away, I'll do the tests on 2023-12-30 and report the result
> then.
>
That would be great, thanks for your offer.
In principle my modifications should be transparent to the AS73211 and
only the code to retrieve the scales has suffered significant
modifications, which I could test with i2c tools.
But none of my tests can compare to yours with real hardware, so I am
looking forward to hearing from you again. Hopefully to hear that I did
not cause any regression :)
Best regards,
Javier Carrasco
prev parent reply other threads:[~2023-12-23 19:45 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
2023-12-23 12:18 ` [PATCH 0/2] iio: light: add support for AMS AS7331 Christian Eggers
2023-12-23 19:45 ` Javier Carrasco [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=acb74002-31ee-4130-96e1-9ac497a15c2e@gmail.com \
--to=javier.carrasco.cruz@gmail.com \
--cc=ceggers@arri.de \
--cc=ceggers@gmx.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).