From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: Taha Ed-Dafili <0rayn.dev@gmail.com>,
linux-iio@vger.kernel.org, rdunlap@infradead.org,
skhan@linuxfoundation.org, nuno.sa@analog.com, andy@kernel.org,
corbet@lwn.net, lars@metafoo.de, Michael.Hennerich@analog.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/5] iio: accel: adxl345: Implement event scaling and ABI compliance
Date: Sun, 1 Mar 2026 12:05:24 +0000 [thread overview]
Message-ID: <20260301120524.710676e5@jic23-huawei> (raw)
In-Reply-To: <f697a233-2fde-49e8-8c85-dbcf2599eaa9@baylibre.com>
On Sat, 28 Feb 2026 10:27:35 -0600
David Lechner <dlechner@baylibre.com> wrote:
> On 2/26/26 9:11 AM, Taha Ed-Dafili wrote:
> > This series addresses ADXL345 driver non-compliance with the IIO ABI.
> >
> Reviewed-by: David Lechner <dlechner@baylibre.com>
>
Updated to add your tag.
Thanks,
J
prev parent reply other threads:[~2026-03-01 12:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 15:11 [PATCH v6 0/5] iio: accel: adxl345: Implement event scaling and ABI compliance Taha Ed-Dafili
2026-02-26 15:11 ` [PATCH v6 1/5] docs: iio: adxl345: grammar and formatting cleanups Taha Ed-Dafili
2026-02-26 15:11 ` [PATCH v6 2/5] iio: core: Add IIO_EV_INFO_SCALE to event info Taha Ed-Dafili
2026-02-26 15:11 ` [PATCH v6 3/5] iio: accel: adxl345: Expose IIO_EV_INFO_VALUE for double tap Taha Ed-Dafili
2026-02-26 15:11 ` [PATCH v6 4/5] iio: accel: adxl345: Implement event scaling for ABI compliance Taha Ed-Dafili
2026-02-26 15:11 ` [PATCH v6 5/5] docs: iio: adxl345: update event attributes and scaling math Taha Ed-Dafili
2026-02-28 16:14 ` [PATCH v6 0/5] iio: accel: adxl345: Implement event scaling and ABI compliance Jonathan Cameron
2026-02-28 16:27 ` David Lechner
2026-03-01 12:05 ` Jonathan Cameron [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=20260301120524.710676e5@jic23-huawei \
--to=jic23@kernel.org \
--cc=0rayn.dev@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=corbet@lwn.net \
--cc=dlechner@baylibre.com \
--cc=lars@metafoo.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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