From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Arnav Kapoor <kapoorarnav43@gmail.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"Gwendal Grignou" <gwendal@chromium.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: add a reviewer entry for the Semtech SX9xxx proximity drivers
Date: Tue, 17 Nov 2026 12:47:54 +0200 [thread overview]
Message-ID: <avww2kChMteEjGnV@ashevche-desk.local> (raw)
In-Reply-To: <20261117094737.15253-1-kapoorarnav43@gmail.com>
On Tue, Nov 17, 2026 at 03:17:35PM +0530, Arnav Kapoor wrote:
> The Semtech SX9310, SX9324, SX9360 and SX9500 proximity sensor drivers
> and the shared sx_common code have no MAINTAINERS entry, so
> get_maintainer.pl only lists the IIO maintainers and reviewers for them.
>
> Add an entry with me as reviewer. There is no M: line, so maintenance
> falls back to the IIO subsystem entry, as Jonathan suggested.
> Link: https://lore.kernel.org/all/20261117031830.69ac22f5@jic23-hlaptop/
This is unreferred in the text above, so orphaned Link tag.
Make it Link: $URL [1] and refer in the text, so we will understand why it's
here.
...
> +F: Documentation/devicetree/bindings/iio/proximity/semtech,sx9310.yaml
> +F: Documentation/devicetree/bindings/iio/proximity/semtech,sx9324.yaml
> +F: Documentation/devicetree/bindings/iio/proximity/semtech,sx9360.yaml
> +F: Documentation/devicetree/bindings/iio/proximity/semtech,sx9500.yaml
These have maintainer field inside each of the file (it's a requirement
by DT AFAIR). So, if you want, you probably need to add yourself inside
each of that as maintainer.
...
> +F: drivers/iio/proximity/sx_common.c
> +F: drivers/iio/proximity/sx_common.h
.* ?
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-11-17 10:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 9:47 Arnav Kapoor
2026-11-17 10:47 ` Andy Shevchenko [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=avww2kChMteEjGnV@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=gwendal@chromium.org \
--cc=jic23@kernel.org \
--cc=kapoorarnav43@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.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
all inboxes | Powered by JetHome®