From: Maxwell Doose <m32285159@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Andy Shevchenko <andriy.shevchenko@intel.com>,
"open list" <linux-iio@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
tduszyns@gmail.com
Subject: Re: [RFC] Maintenance status of SPS30 driver and related Tomasz Duszynski entries
Date: Tue, 9 Jun 2026 10:21:59 -0500 [thread overview]
Message-ID: <20260609102159.14c68a8e@linuxescape> (raw)
In-Reply-To: <20260609140712.2e5d1640@jic23-huawei>
On Tue, 9 Jun 2026 14:07:12 +0100
Jonathan Cameron <jic23@kernel.org> wrote:
> On Mon, 8 Jun 2026 08:57:54 -0500
> Maxwell Doose <m32285159@gmail.com> wrote:
>
> > Hi all,
> >
> > On Sun, 10 May 2026 10:12:09 +0300
> > Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
> >
> > > On Sat, May 09, 2026 at 07:14:35PM -0500, Maxwell Doose wrote:
> > >
> > > If email is not bouncing, let give him time to response. If there is no
> > > response in a reasonable time (usually up to month in the summer time
> > > due to people usually have long vacations), then we can act accordingly.
> > >
> >
> > It's been about a month now with no response. I believe it may be time
> > to make a decision about who becomes the new maintainers of his
> > drivers.
> >
>
> Send a patch. Won't go upstream until next cycle anyway so plenty of
> time for any late feedback
>
Alrighty then. I'll probably take his chemical/ drivers since I've
been spending some time in there. Regarding his light/ driver (ROHM
BH1750 AMBIENT LIGHT SENSOR DRIVER) I can take it but I want to see if
anyone else wants to first.
--
best regards,
max
prev parent reply other threads:[~2026-06-09 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-10 0:14 [RFC] Maintenance status of SPS30 driver and related Tomasz Duszynski entries Maxwell Doose
2026-05-10 7:12 ` Andy Shevchenko
2026-05-10 7:16 ` Maxwell Doose
2026-06-08 13:57 ` Maxwell Doose
2026-06-09 13:07 ` Jonathan Cameron
2026-06-09 15:21 ` Maxwell Doose [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=20260609102159.14c68a8e@linuxescape \
--to=m32285159@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tduszyns@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.