From: Tomasz Duszynski <tduszyns@gmail.com>
To: andriy.shevchenko@intel.com
Cc: andy@kernel.org, dlechner@baylibre.com, jic23@kernel.org,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
m32285159@gmail.com, nuno.sa@analog.com, tduszyns@gmail.com
Subject: Re: [PATCH v2 1/2] iio: chemical: sps30: update email
Date: Thu, 18 Jun 2026 18:21:39 +0200 [thread overview]
Message-ID: <20260618162139.124562-1-tduszyns@gmail.com> (raw)
In-Reply-To: <ajOXKKDWrTURPpro@ashevche-desk.local>
> On Wed, Jun 17, 2026 at 07:27:15PM +0200, Tomasz Duszynski wrote:
> > The old email has been inactive for a while. Replace all occurrences
> > with the current address.
>
> ...
>
> > .mailmap | 1 +
> > drivers/iio/chemical/sps30_i2c.c | 4 ++--
> > drivers/iio/chemical/sps30_serial.c | 4 ++--
>
> I don't care much, but the cleaner approach is to have a separate patch
> for .mailmap and put it at the end of the series. Otherwise it's confusing
> that it's related to a certain driver, while changes are applied across
> the whole tree.
No strong opinions on the change itself, maybe except patch ordering.
I'd rather see mail mapping update placed before driver changes to make
sure it is visible if bisect ends up in the middle of the series.
next prev parent reply other threads:[~2026-06-18 16:28 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 [this message]
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
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=20260618162139.124562-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
all inboxes | Powered by JetHome®