From: Maxwell Doose <m32285159@gmail.com>
To: "Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-iio@vger.kernel.org (open list:IIO SUBSYSTEM AND DRIVERS),
devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND
FLATTENED DEVICE TREE BINDINGS),
linux-kernel@vger.kernel.org (open list)
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Replace Tomasz Duszynski as maintainer for SPS30
Date: Tue, 9 Jun 2026 11:16:59 -0500 [thread overview]
Message-ID: <20260609161701.52513-2-m32285159@gmail.com> (raw)
Hi all.
This is basically the 2nd half of replacing Tomasz's entries, once
again, in the SPS30 dt-bindings and his entry in MAINTAINERS. All of his
entries across IIO appear to be dead, which is why this is being sent.
Jonathan Cameron's approved of this [1] so his entries in iio are being
replaced and an RFC regarding this topic with Tomasz Cced has been
sitting on lore.kernel.org for about a month now.
Maxwell Doose (2):
dt-bindings: iio: sensirion,sps30: Add myself as maintainer
MAINTAINERS: Add myself as maintainer for SPS30
.../devicetree/bindings/iio/chemical/sensirion,sps30.yaml | 2 +-
MAINTAINERS | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
[1] https://lore.kernel.org/linux-iio/20260609140712.2e5d1640@jic23-huawei/
--
2.54.0
next reply other threads:[~2026-06-09 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 16:16 Maxwell Doose [this message]
2026-06-09 16:17 ` [PATCH 1/2] dt-bindings: iio: sensirion,sps30: Add myself as maintainer Maxwell Doose
2026-06-09 16:17 ` [PATCH 2/2] MAINTAINERS: Add myself as maintainer for SPS30 Maxwell Doose
2026-06-09 16:22 ` [PATCH 0/2] Replace Tomasz Duszynski " David Lechner
2026-06-09 16:41 ` 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=20260609161701.52513-2-m32285159@gmail.com \
--to=m32285159@gmail.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
/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