From: Tomasz Duszynski <tduszyns@gmail.com>
To: m32285159@gmail.com
Cc: andriy.shevchenko@intel.com, andy@kernel.org,
dlechner@baylibre.com, jic23@kernel.org,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
nuno.sa@analog.com, tduszyns@gmail.com
Subject: Re: [PATCH v2 0/2] iio: chemical: sps30, scd30
Date: Wed, 24 Jun 2026 18:01:25 +0200 [thread overview]
Message-ID: <20260624160137.131207-1-tduszyns@gmail.com> (raw)
In-Reply-To: <CAKqfh0GF1WCF_85r4F0FTvwEdBPoihynx2VHmT+CtyDfYoRDbQ@mail.gmail.com>
> On Thu, Jun 18, 2026 at 10:40 AM Maxwell Doose <m32285159@gmail.com> wrote:
> >
> > On Wed, Jun 17, 2026 at 12:22 PM Tomasz Duszynski <tduszyns@gmail.com> wrote:
> > >
> > > This series replaces old email addresses with a current one to
> > > make sure changes show up in my mailbox.
> > >
> > > v2:
> > > - add missing mailmap entry
> > >
> > > Tomasz Duszynski (2):
> > > iio: chemical: sps30: update email
> > > iio: chemical: scd30: update email
> > >
> >
> > Even though you were the previous maintainer I should probably still
> > ack this for the scd30 for good measure, so for scd30 patches:
> >
> > Acked-by: Maxwell Doose <m32285159@gmail.com>
>
> I also neglected to mention this but I updated your entry in the
> dt-bindings for this so you may want to go and add yourself to that as
> well.
Yup, I'll modify that too for completeness.
prev parent reply other threads:[~2026-06-24 16:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 17:21 [PATCH v2 0/2] iio: chemical: sps30, scd30 Tomasz Duszynski
2026-06-17 17:27 ` [PATCH v2 1/2] iio: chemical: sps30: update email Tomasz Duszynski
2026-06-18 6:58 ` Andy Shevchenko
2026-06-18 16:21 ` Tomasz Duszynski
2026-06-18 17:53 ` Andy Shevchenko
2026-06-17 17:27 ` [PATCH v2 2/2] iio: chemical: scd30: " Tomasz Duszynski
2026-06-18 6:59 ` [PATCH v2 0/2] iio: chemical: sps30, scd30 Andy Shevchenko
2026-06-18 15:40 ` Maxwell Doose
2026-06-18 21:27 ` Maxwell Doose
2026-06-24 16:01 ` Tomasz Duszynski [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=20260624160137.131207-1-tduszyns@gmail.com \
--to=tduszyns@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m32285159@gmail.com \
--cc=nuno.sa@analog.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