Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Maxwell Doose <m32285159@gmail.com>
Cc: Stepan Ionichev <sozdayvek@gmail.com>,
	dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: scd30: orphan the driver
Date: Thu, 7 May 2026 17:09:50 +0100	[thread overview]
Message-ID: <20260507170950.37a46820@jic23-huawei> (raw)
In-Reply-To: <CAKqfh0EZ_Tku4DK1F-J_UNTDzgmKshbOQS889Dpf8sbChm-LrA@mail.gmail.com>

On Wed, 6 May 2026 13:58:46 -0500
Maxwell Doose <m32285159@gmail.com> wrote:

> On Wed, May 6, 2026 at 1:30 PM Stepan Ionichev <sozdayvek@gmail.com> wrote:
> >
> > The maintainer email tomasz.duszynski@octakon.com bounces with
> > "The email account that you tried to reach does not exist", and
> > the author has had no commits in the kernel tree for years. The
> > driver is in practice maintained on an ad-hoc basis by the IIO
> > subsystem maintainers and contributors who happen to send patches
> > against it.
> >
> > Drop the stale M: line and mark the entry as Orphan so that future
> > patch submitters and get_maintainer.pl no longer try to deliver
> > mail to a dead address.
> >
> > The F: entries are kept so MAINTAINERS still describes the file
> > set covered by the IIO subsystem (linux-iio@vger.kernel.org).
> >
> > Signed-off-by: Stepan Ionichev <sozdayvek@gmail.com>
> > ---
> >  MAINTAINERS | 3 +--
> >  1 file changed, 1 insertion(+), 2 deletions(-)
> >  
> [snip]
> >  
> 
> Hi Stepan, Jonathan,
> 
> I saw this was getting orphaned, and I was wondering if I could step
> up as maintainer. I think it would be an interesting challenge but I
> think I could do it, I've been doing a whole lot of stuff across iio.
> I don't have the hardware but I'd be happy to step up to keep this
> driver up-to-date.
> 
> best regards,
> max

Fine by me.  It is a reasonably easy to get part so if anything complex
comes up might be worth getting one.  Feel free to shout if that becomes
necessary and you need help getting hold of it.

Jonathan

      reply	other threads:[~2026-05-07 16:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-06 18:29 [PATCH] MAINTAINERS: scd30: orphan the driver Stepan Ionichev
2026-05-06 18:58 ` Maxwell Doose
2026-05-07 16:09   ` 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=20260507170950.37a46820@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m32285159@gmail.com \
    --cc=nuno.sa@analog.com \
    --cc=sozdayvek@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