From: "Nuno Sá" <noname.nuno@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Andy Shevchenko <andriy.shevchenko@intel.com>,
Sanjay Chitroda <sanjayembeddedse@gmail.com>,
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 1/5] MAINTAINERS: Update Analog Devices IIO drivers entry
Date: Thu, 7 May 2026 09:09:08 +0100 [thread overview]
Message-ID: <afxIT92xmV4bM-4T@nsa> (raw)
In-Reply-To: <20260504172247.58e833d8@jic23-huawei>
On Mon, May 04, 2026 at 05:22:47PM +0100, Jonathan Cameron wrote:
> On Mon, 4 May 2026 10:35:53 +0300
> Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
>
> > On Fri, May 01, 2026 at 10:05:11AM +0100, Nuno Sá wrote:
> > > On Fri, 2026-05-01 at 00:36 +0530, Sanjay Chitroda wrote:
> >
> > > > Lars-Peter Clausen is currently busy and is therefore removed from the
> > > > ANALOG DEVICES INC IIO DRIVERS entry, with input from Jonathan.
> > > >
> > > > Add Analog Devices mailing list as contact for the ANALOG DEVICES INC
> > > > IIO DRIVERS entry for coverage support.
> >
> > ...
> >
> > > > ANALOG DEVICES INC IIO DRIVERS
> > > > -M: Lars-Peter Clausen <lars@metafoo.de>
> > >
> > > I honestly got the impression that for the entries that had individual maintainers,
> > > we would not touch them but maybe I lost track of the discussion. Anwýways, if we are
> > > just relying on this, then I need to put in here given that these day I'm the one
> > > taking more care of the mainline stuff.
> >
> > > > M: Michael Hennerich <Michael.Hennerich@analog.com>
> > > > +L: linux@analog.com
> >
> > My reading of this patch that you, guys (ADI), have a public ML / distribution
> > list that you manage now inside the corp. Whoever is in that list is
> > automatically will be a potential reviewer. However, it doesn't prevent
> > (and I actually fully support that) that ADI nominates more Designated
> > Reviewers and/or Maintainers.
>
> My intent was:
> 1) This entry one got fleshed out to add the list - given it's a catch all
> that 'should' get added to all ADI related patches (similar to the catch
> all IIO list adding the linux-iio@vger.kernel.org list and myself +
> the 3 reviewers listed there).
> 2) Any ADI entries that due to stale emails would have no one listed,
> were removed so that this catch all was the source of truth.
>
> I'm very happy if Nuno is willing to be added to the top level ADI IIO
> entry now Lars-Peter is off doing other fun things.
Yes, it makes sense to add me in there.
- Nuno Sá
>
> I'm also very happy to see any additional individual driver entrees that get
> more people on the hook for reviewing :)
>
> Jonathan
>
> >
> > > > S: Supported
> > > > W: http://wiki.analog.com/
> > > > W: https://ez.analog.com/linux-software-drivers
> >
>
next prev parent reply other threads:[~2026-05-07 8:08 UTC|newest]
Thread overview: 18+ 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-05-07 8:09 ` Nuno Sá [this message]
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 ` [PATCH v4 0/5] MAINTAINERS: update iio adi entry and drop redundant entry Andy Shevchenko
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=afxIT92xmV4bM-4T@nsa \
--to=noname.nuno@gmail.com \
--cc=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