From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Maxwell Doose <m32285159@gmail.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
"open list:PNI RM3100 IIO DRIVER" <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: Sun, 10 May 2026 10:12:09 +0300 [thread overview]
Message-ID: <agAvydze87mMLaVC@ashevche-desk.local> (raw)
In-Reply-To: <CAKqfh0GxasvVEMVySviw5vB1QmbNF-RKBjuoMD9ffEtnQjDkJQ@mail.gmail.com>
On Sat, May 09, 2026 at 07:14:35PM -0500, Maxwell Doose wrote:
> I was preparing some other patches for the sps30 and scd30 and
> realized that Tomasz Duszynski (whom we've already considered
> inactive) is still listed as maintainer of the sps30 and some other
> drivers under a different email. I sent a patch for the sps30 and
> while his email didn't bounce, I still have reason to believe he's
> inactive as according to git log --author="Tomasz Duszynski", he
> hasn't had a commit in a little over 3 years, which means the drivers
> he's maintaining are essentially orphans. I'd be willing to maintain
> them but I just wanted your input before we consider anything.
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.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-05-10 7:12 UTC|newest]
Thread overview: 4+ 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 [this message]
2026-05-10 7:16 ` Maxwell Doose
2026-06-08 13:57 ` Maxwell Doose
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=agAvydze87mMLaVC@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m32285159@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox