From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Sanjay Chitroda <sanjayembeddedse@gmail.com>
Cc: jic23@kernel.org, dlechner@baylibre.com, nuno.sa@analog.com,
lars@metafoo.de, andy@kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/5] MAINTAINERS: update iio adi entry and drop redundant entry
Date: Mon, 4 May 2026 10:40:07 +0300 [thread overview]
Message-ID: <afhNV4Ja60rxk-rp@ashevche-desk.local> (raw)
In-Reply-To: <20260430190642.3434650-1-sanjayembedded@gmail.com>
On Fri, May 01, 2026 at 12:36:37AM +0530, Sanjay Chitroda wrote:
> Following suggestion from Jonathan and ack from Nuno, prepare change
> to add linux@analog.com list to has always valid coverage for INC IIO
> drivers and drop redundant entry and make sure same has been catch by
> the wildcard paths under ANALOG DEVICES INC IIO DRIVERS.
>
> Around 40 entries are redundant which is covered by wildcard, to easy
> the review process split entry in multiple
> MAINTAINERS: iio: adi: consolidate entries changes;
> based on mutual understanding we can fix/squash entries.
I think you may not do that (at least as easy as this series).
NAK from me in this form due to the individual records having different
maintainers that are not listed in the end result. So, what you need to
do is to split this per driver (record). Grouping is only possible when
the same (or subset of the same) people are maintaining the individual
driver, like all drivers that are under Nuno and David (in the condition
that they become maintainers and/or designated reviewers of the whole
thing).
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-05-04 7:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 19:06 [PATCH v4 0/5] MAINTAINERS: update iio adi entry and drop redundant entry Sanjay Chitroda
2026-04-30 19:06 ` [PATCH v4 1/5] MAINTAINERS: Update Analog Devices IIO drivers entry Sanjay Chitroda
2026-05-01 9:05 ` Nuno Sá
2026-05-04 7:35 ` Andy Shevchenko
2026-05-04 16:22 ` Jonathan Cameron
2026-04-30 19:06 ` [PATCH v4 2/5] MAINTAINERS: iio: adi: consolidate entries Sanjay Chitroda
2026-05-04 16:24 ` Jonathan Cameron
2026-05-05 2:30 ` Sanjay Chitroda
2026-05-05 9:04 ` Andy Shevchenko
2026-05-05 10:54 ` Jonathan Cameron
2026-05-05 11:55 ` Sanjay Chitroda
2026-05-05 12:41 ` Andy Shevchenko
2026-05-05 16:15 ` Jonathan Cameron
2026-04-30 19:06 ` [PATCH v4 3/5] " Sanjay Chitroda
2026-04-30 19:06 ` [PATCH v4 4/5] " Sanjay Chitroda
2026-04-30 19:06 ` [PATCH v4 5/5] " Sanjay Chitroda
2026-05-04 7:40 ` 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=afhNV4Ja60rxk-rp@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=sanjayembeddedse@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