From: Arnav Kapoor <kapoorarnav43@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Gwendal Grignou" <gwendal@chromium.org>,
"Stephen Boyd" <swboyd@chromium.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] iio: proximity: sx9310/sx9360: reject out-of-range hardware gain values
Date: Sun, 15 Nov 2026 07:13:32 +0530 [thread overview]
Message-ID: <20261115014333.120063-1-kapoorarnav43@gmail.com> (raw)
In-Reply-To: <avXeSbAEGhkMjMJa@ashevche-desk.local>
On Thu, Nov 12, 2026 at 05:42:01PM +0200, Andy Shevchenko wrote:
> Now it looks better.
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
Thanks, Andy.
Jonathan, a related question while this thread has the right people
on it: the Semtech SX9xxx proximity drivers (sx9310, sx9324, sx9360,
sx9500 and sx_common) have no MAINTAINERS entry, so get_maintainer.pl
only finds the IIO maintainers and reviewers for them.
I've been working through bugs in these drivers for the last few weeks
and would like to keep doing that. Would you be OK with a patch that
adds a "SEMTECH SX9XXX PROXIMITY SENSOR DRIVERS" entry with me as R:,
or M: if you'd prefer the drivers to have a maintainer?
Gwendal, as the author of most of this code, you'd be very welcome on
the entry too, if you want to be listed.
I don't have the hardware, so anything that needs a real device would
still need someone who has one.
Thanks,
Arnav
prev parent reply other threads:[~2026-11-15 1:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 16:40 Arnav Kapoor
2026-11-11 16:40 ` [PATCH v3 1/2] iio: proximity: sx9310: " Arnav Kapoor
2026-11-11 16:40 ` [PATCH v3 2/2] iio: proximity: sx9360: " Arnav Kapoor
2026-11-13 1:53 ` Jonathan Cameron
2026-11-12 15:42 ` [PATCH v3 0/2] iio: proximity: sx9310/sx9360: " Andy Shevchenko
2026-11-15 1:43 ` Arnav Kapoor [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=20261115014333.120063-1-kapoorarnav43@gmail.com \
--to=kapoorarnav43@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=gwendal@chromium.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=swboyd@chromium.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
all inboxes | Powered by JetHome®