From: Sanjay Chitroda <sanjayembeddedse@gmail.com>

Hi all,

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.

Changes in v4:
- Use ANALOG DEVICES INC IIO entry to catch all entry of drivers where
  there is no explicit maintainer then drop that redundant entry
- Prepare series of change(s) as suggseted by Jonathan
- v3 link -> https://lore.kernel.org/all/20260421165856.2245598-1-sanjayembedded@gmail.com/
Changes in v3:
- Following input from Nuno and confirmation from Jonathan,
  replacing domain specific maintainer with mailing list.
- v1 link -> https://lore.kernel.org/all/20260418211336.1800221-1-sanjayembedded@gmail.com/

Thanks,
Sanjay Chitroda

Sanjay Chitroda (5):
  MAINTAINERS: Update Analog Devices IIO drivers entry
  MAINTAINERS: iio: adi: consolidate entries
  MAINTAINERS: iio: adi: consolidate entries
  MAINTAINERS: iio: adi: consolidate entries
  MAINTAINERS: iio: adi: consolidate entries

 MAINTAINERS | 386 +---------------------------------------------------
 1 file changed, 4 insertions(+), 382 deletions(-)


base-commit: 39b80c5c9830d12d2d6531059001301c4265322a
-- 
2.34.1

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