From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Joshua Crofts <joshua.crofts1@gmail.com>,
Maxwell Doose <m32285159@gmail.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Andy Shevchenko <andriy.shevchenko@intel.com>,
open list <linux-iio@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
tduszyns@gmail.com, heikki.haikola@fi.rohmeurope.com,
antti.sakkinen@fi.rohmeurope.com
Subject: Re: [RFC] Maintenance status of SPS30 driver and related Tomasz Duszynski entries
Date: Thu, 25 Jun 2026 08:11:17 +0300 [thread overview]
Message-ID: <09dea87f-d2e2-4bbf-a948-3092a2dae29a@gmail.com> (raw)
In-Reply-To: <a2b1acbb-f8f2-4d6f-9681-986f42feddfa@gmail.com>
On 10/06/2026 12:46, Matti Vaittinen wrote:
> On 10/06/2026 11:36, Joshua Crofts wrote:
>> On Tue, 9 Jun 2026 10:21:59 -0500
>> Maxwell Doose <m32285159@gmail.com> wrote:
>>> 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.
>>>
>>
>> I believe that there are a few ROHM folk in IIO, perhaps they would take
>> interest in maintaining the driver.
>>
>
> Thanks for pinging me. I need to see if we have any of the:BH1710,
> BH1715, BH1721, BH1750 or BH1751 here - and if we don't, then I need to
> ask from the HQ.
The HQ promised to provide me BH1721 and BH1751 so I am fine maintaining
(S:) this driver.
Yours,
-- Matti
--
Matti Vaittinen
Linux kernel developer at ROHM Semiconductors
Oulu Finland
~~ When things go utterly wrong vim users can always type :help! ~~
prev parent reply other threads:[~2026-06-25 5:11 UTC|newest]
Thread overview: 9+ 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
2026-06-10 8:36 ` Joshua Crofts
2026-06-10 9:46 ` Matti Vaittinen
2026-06-25 5:11 ` Matti Vaittinen [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=09dea87f-d2e2-4bbf-a948-3092a2dae29a@gmail.com \
--to=mazziesaccount@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=antti.sakkinen@fi.rohmeurope.com \
--cc=heikki.haikola@fi.rohmeurope.com \
--cc=jic23@kernel.org \
--cc=joshua.crofts1@gmail.com \
--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