From: Jonathan Cameron <jic23@kernel.org>
To: Siddharth Menon <simeddon@gmail.com>
Cc: linux-iio@vger.kernel.org, marcelo.schmitt1@gmail.com,
gregkh@linuxfoundation.org, lars@metafoo.de,
Michael.Hennerich@analog.com, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev, lars@metafoo.d
Subject: Re: [PATCH 0/2] iio: accel: adis16203: cleanup and standardization
Date: Sat, 8 Mar 2025 14:49:44 +0000 [thread overview]
Message-ID: <20250308144944.668d79b5@jic23-huawei> (raw)
In-Reply-To: <20250308144357.20f24fa6@jic23-huawei>
On Sat, 8 Mar 2025 14:43:57 +0000
Jonathan Cameron <jic23@kernel.org> wrote:
> On Wed, 5 Mar 2025 20:59:10 +0530
> Siddharth Menon <simeddon@gmail.com> wrote:
>
> > This series improves the adis16203 driver by using standard unit macros
> > and removing an unused spi_set_drvdata() call.
> >
> > Siddharth Menon (2):
> > iio: accel: adis16203: Use units.h macros for voltage values
> > iio: accel: adis16203: Remove spi_set_drvdata()
> >
> > drivers/staging/iio/accel/adis16203.c | 9 ++++-----
> > 1 file changed, 4 insertions(+), 5 deletions(-)
> >
>
> I'm not going to apply these because I think you correct
> identified that the device support should just be added
> to the adis16201 driver and this one dropped.
> Good thing you were more awake on this than me ;)
>
Sorry - wrong person.
https://lore.kernel.org/all/20250306002645.1555569-1-danascape@gmail.com/
I'm definitely not awake today.
Jonathan
> Jonathan
next prev parent reply other threads:[~2025-03-08 14:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 15:29 [PATCH 0/2] iio: accel: adis16203: cleanup and standardization Siddharth Menon
2025-03-05 15:29 ` [PATCH 1/2] iio: accel: adis16203: Use units.h macros for measurements Siddharth Menon
2025-03-05 15:29 ` [PATCH 2/2] iio: accel: adis16203: remove spi_set_drvdata() Siddharth Menon
2025-03-08 14:43 ` [PATCH 0/2] iio: accel: adis16203: cleanup and standardization Jonathan Cameron
2025-03-08 14:49 ` Jonathan Cameron [this message]
2025-03-09 5:48 ` Siddharth Menon
2025-03-09 16:27 ` Jonathan Cameron
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=20250308144944.668d79b5@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=gregkh@linuxfoundation.org \
--cc=lars@metafoo.d \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=marcelo.schmitt1@gmail.com \
--cc=simeddon@gmail.com \
/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