From: Jonathan Cameron <jic23@kernel.org>
To: Sanjay Chitroda <sanjayembeddedse@gmail.com>
Cc: "Nuno Sá" <noname.nuno@gmail.com>,
nuno.sa@analog.com, linux-iio@vger.kernel.org,
demonsingur@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] MAINTAINERS: Update maintainer for iio driver(s)
Date: Tue, 28 Apr 2026 19:11:18 +0100 [thread overview]
Message-ID: <20260428191118.0270cb0a@jic23-huawei> (raw)
In-Reply-To: <577DD2DD-76ED-4A7D-AB13-6008FE2AFCF4@gmail.com>
On Mon, 27 Apr 2026 17:50:26 +0530
Sanjay Chitroda <sanjayembeddedse@gmail.com> wrote:
> On 26 April 2026 6:46:45 pm IST, Jonathan Cameron <jic23@kernel.org> wrote:
> >On Sun, 26 Apr 2026 15:21:47 +0530
> >Sanjay Chitroda <sanjayembeddedse@gmail.com> wrote:
> >
> >> On 25 April 2026 12:57:27 am IST, Jonathan Cameron <jic23@kernel.org> wrote:
> >> >On Fri, 24 Apr 2026 09:08:37 +0100
> >> >Nuno Sá <noname.nuno@gmail.com> wrote:
> >> >
> >> >> On Fri, Apr 24, 2026 at 07:22:37AM +0530, Sanjay Chitroda wrote:
> >> >> >
> >> >> >
> >> >> > On 23 April 2026 1:46:32 pm IST, "Nuno Sá" <noname.nuno@gmail.com> wrote:
> >> >> > >On Tue, Apr 21, 2026 at 10:28:56PM +0530, Sanjay Chitroda wrote:
> >> >> > >> From: Sanjay Chitroda <sanjayembeddedse@gmail.com>
> >> >> > >>
> >> >> > >> The listed maintainer analog domain email for Cosmin Tanislav is no
> >> >> > >> longer valid, and he would no longer maintain this driver(s).
> >> >> > >>
> >> >> > >> Replacing email maintainer with list, to keep it valid all the time.
> >> >> > >>
> >> >> > >> Signed-off-by: Sanjay Chitroda <sanjayembeddedse@gmail.com>
> >> >> > >> ---
> >> >> > >> Changes in v3:
> >> >> > >> - Following input from Nuno and confirmation from Jonathan,
> >> >> > >> replacing domain specific maintainer with mailing list.
> >> >> > >> - Link to v1: https://lore.kernel.org/all/20260418211336.1800221-1-sanjayembedded@gmail.com/
> >> >> > >> ---
> >> >> > >
> >> >> > >While you're doing this, could you take the opportunity and also update
> >> >> > >this entry?
> >> >> > >
> >> >> > >https://elixir.bootlin.com/linux/v7.0/source/MAINTAINERS#L1837
> >> >> > >
> >> >> > >Thanks!
> >> >> > >- Nuno Sá
> >> >> > >
> >> >> > Hi Nuno Sá,
> >> >> >
> >> >> > Are you suggesting to have separate change to add mailing list in analog devices and iio driver which you pointed ?
> >> >> >
> >> >> > This change is specific to email debounce due to Cosmin analog domain account.
> >> >>
> >> >> Yes, it makes more sense for it to be a separate patch. I also suggested
> >> >> that one because it's an entry covering a lot of driver's and
> >> >> includes Lars which has been silent for some time now so maybe it's better no
> >> >> to "spam" him like that :)
> >> >
> >> >If we are adding the entry to the catch all, do these individual entries
> >> >bring any benefit. Maybe we should just drop them?
> >> >
> >>
> >> Hi Nuno and Jonathan,
> >>
> >> Here is my view on this,
> >>
> >> Lars-peter is maintainer of drivers falls in different subsystem, so
> >> If we can plan to drop/replace would need ack from Lars-peter and
> >> also mutual agreement from all respective subsystem owner as it won't
> >> be advisable just to update analog devices IIO drivers maintainer.
> >
> >Definitely good to get Lars' view on this - though that can be on the
> >final patch. He is indeed busy with other thing these days so
> >for IIO at least, if Lars doesn't respond for a while I can take
> >a patch dropping him as the maintainer (and move to Credits) anyway.
> >
> >>
> >> Regarding analog mailing list, we can plan to add list across
> >> MAINTAINERS where analog devices ownership is there as maintainer or
> >> reviewer.
> >No. I'm proposing we add it to
> >
> >ANALOG DEVICES INC IIO DRIVERS
> >M: Lars-Peter Clausen <lars@metafoo.de>
> >M: Michael Hennerich <Michael.Hennerich@analog.com>
> >S: Supported
> >W: http://wiki.analog.com/
> >W: https://ez.analog.com/linux-software-drivers
> >F: Documentation/ABI/testing/sysfs-bus-iio-frequency-ad9523
> >F: Documentation/ABI/testing/sysfs-bus-iio-frequency-adf4350
> >F: Documentation/devicetree/bindings/iio/*/adi,*
> >F: Documentation/devicetree/bindings/iio/adc/lltc,ltc2496.yaml
> >F: Documentation/devicetree/bindings/iio/adc/lltc,ltc2497.yaml
> >F: Documentation/iio/ad7606.rst
> >F: drivers/iio/*/ad*
> >F: drivers/iio/adc/ltc249*
> >F: drivers/iio/amplifiers/hmc425a.c
> >F: drivers/staging/iio/*/ad*
> >X: drivers/iio/*/adjd*
> >
> >Only and for entries that match those wildcards and where there is not
> >other info (such as the ones here post modification) just delete the
> >more specific entry.
> >
> Hi Jonathan,
>
> I agree with your point.
> It make sense to drop redundant entry when we are using catch all.
>
> Also, with your suggested approach.
> This change won't make any sense as this entries would also get as driver files are included with wildcard.
>
> I would prepare and share changes with your suggested approach:
>
> Needs your confirmation/input on two point
> 1. Drop this change and have new with suggested or keep this change and on top of this apply your suggestion
Probably spin it as 2 fresh patches - suggested-by fine though minor enough I don't really
care!
1. Add the list to the entry as above and drop Lars-Peter's entry.
2. Delete the ones with stale maintainers, making sure to state in the patch description
that they are covered by the broader catch all.
> 2. Many entries include Documentation and include files, that also required to in-corporate in ADI entry with specific path or wildcard based on file paths, correct ?
If covered by other entries no need to update anything. If missed by the wild
cards and not covered elsewhere then we need a wider set of matches for the
one above.
Thanks for sorting this out!
J
>
>
> >Where we have maintainers for specific drivers then we keep the entries.
> >No need to sorry too much about adding this list to all of those ADI
> >drivers as this catch all should also match.
> >
> >So end result of the proposed change would be to just remove the entrees
> >you are updating here as the catch all will cover them.
> >
> >Thanks,
> >
> >Jonathan
> >
> >>
> >> Also, this change would be separate from both above points so we
> >> shall take it further.
> >>
> >> Kindly share your thoughts, valuable input and guidance on how should
> >> we proceed further for this change and other two topics.
> >>
> >> Thanks,
> >> Sanjay Chitroda
> >>
> >> >>
> >> >> >
> >> >> > Also, I had take a glance on MAINTAINERS, it looks there are
> >> >> > good amount of drivers which are maintained by you and Michael
> >> >> > Hennerich from analog. If you suggest I can plan to add analog
> >> >> > mailing list in all respective places in separate change.
> >> >> >
> >> >> > This way all analog device maintained drivers will have mailing
> >> >> > list of analog.com
> >> >>
> >> >> Yeah, I'm not sure if it makes sense to go change all of those. I
> >> >> would focus on bouncing emails and we (ADI) need to make sure to
> >> >> also include that list from now on.
> >> >>
> >> >> - Nuno Sá
> >> >>
> >> >> >
> >> >> > Kindly share your thoughts on the same.
> >> >> >
> >> >> > Thanks,
> >> >> > Sanjay Chitroda
> >> >> >
> >> >> >
> >> >> >
> >> >> > >> MAINTAINERS | 8 ++++----
> >> >> > >> 1 file changed, 4 insertions(+), 4 deletions(-)
> >> >> > >>
> >> >> > >> diff --git a/MAINTAINERS b/MAINTAINERS
> >> >> > >> index c981cbdff500..6498f0aed1ff 100644
> >> >> > >> --- a/MAINTAINERS
> >> >> > >> +++ b/MAINTAINERS
> >> >> > >> @@ -644,7 +644,7 @@ F: drivers/iio/accel/adxl355_i2c.c
> >> >> > >> F: drivers/iio/accel/adxl355_spi.c
> >> >> > >>
> >> >> > >> ADXL367 THREE-AXIS DIGITAL ACCELEROMETER DRIVER
> >> >> > >> -M: Cosmin Tanislav <cosmin.tanislav@analog.com>
> >> >> > >> +L: linux@analog.com
> >> >> > >> L: linux-iio@vger.kernel.org
> >> >> > >> S: Supported
> >> >> > >> W: https://ez.analog.com/linux-software-drivers
> >> >> > >> @@ -1461,7 +1461,7 @@ F:
> >> >> > >> Documentation/devicetree/bindings/iio/adc/adi,ad4080.yaml
> >> >> > >> F: drivers/iio/adc/ad4080.c
> >> >> > >> ANALOG DEVICES INC AD4130 DRIVER
> >> >> > >> -M: Cosmin Tanislav <cosmin.tanislav@analog.com>
> >> >> > >> +L: linux@analog.com
> >> >> > >> L: linux-iio@vger.kernel.org
> >> >> > >> S: Supported
> >> >> > >> W: https://ez.analog.com/linux-software-drivers
> >> >> > >> @@ -1549,7 +1549,7 @@ F:
> >> >> > >> Documentation/devicetree/bindings/iio/dac/adi,ad7293.yaml
> >> >> > >> F: drivers/iio/dac/ad7293.c
> >> >> > >> ANALOG DEVICES INC AD74115 DRIVER
> >> >> > >> -M: Cosmin Tanislav <cosmin.tanislav@analog.com>
> >> >> > >> +L: linux@analog.com
> >> >> > >> L: linux-iio@vger.kernel.org
> >> >> > >> S: Supported
> >> >> > >> W: https://ez.analog.com/linux-software-drivers
> >> >> > >> @@ -1557,7 +1557,7 @@ F:
> >> >> > >> Documentation/devicetree/bindings/iio/addac/adi,ad74115.yaml
> >> >> > >> F: drivers/iio/addac/ad74115.c
> >> >> > >> ANALOG DEVICES INC AD74413R DRIVER
> >> >> > >> -M: Cosmin Tanislav <cosmin.tanislav@analog.com>
> >> >> > >> +L: linux@analog.com
> >> >> > >> L: linux-iio@vger.kernel.org
> >> >> > >> S: Supported
> >> >> > >> W: https://ez.analog.com/linux-software-drivers
> >> >> > >> --
> >> >> > >> 2.34.1
> >> >> > >>
> >> >
> >
>
prev parent reply other threads:[~2026-04-28 18:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260421165856.2245598-1-sanjayembedded@gmail.com>
[not found] ` <aenU2WZnVJ-esibn@nsa>
[not found] ` <8C4ED753-72A9-4A34-920D-A5C5E8DB1840@gmail.com>
[not found] ` <aeskNzhWtKPNYb4R@nsa>
[not found] ` <20260424202727.1b880766@jic23-huawei>
[not found] ` <DEE9F0E2-7759-4C58-BF53-2FA8732050B5@gmail.com>
[not found] ` <20260426141645.5fb8406a@jic23-huawei>
2026-04-27 9:08 ` [PATCH v3] MAINTAINERS: Update maintainer for iio driver(s) Nuno Sá
2026-04-27 12:20 ` Sanjay Chitroda
2026-04-28 18:11 ` Jonathan Cameron [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=20260428191118.0270cb0a@jic23-huawei \
--to=jic23@kernel.org \
--cc=demonsingur@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=noname.nuno@gmail.com \
--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