From: sashiko-bot@kernel.org
To: "Maxwell Doose" <m32285159@gmail.com>
Cc: conor+dt@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: iio: chemical: sensiron,scd30: Update maintainers field
Date: Mon, 11 May 2026 11:35:23 +0000 [thread overview]
Message-ID: <20260511113523.BC06BC2BCB0@smtp.kernel.org> (raw)
In-Reply-To: <20260510020758.233721-1-m32285159@gmail.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] The commit fails to update the kernel's central MAINTAINERS file.
- [Low] Typo in the commit subject line prefix.
--
commit 5e371f37c8537ade8dedd4080ab7c1188ea887e6
Author: Maxwell Doose <m32285159@gmail.com>
dt-bindings: iio: chemical: sensiron,scd30: Update maintainers field
This commit updates the maintainers field in the Sensirion SCD30 device
tree binding to replace Tomasz Duszynski with Maxwell Doose.
Link: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git/commit/?h=togreg
> dt-bindings: iio: chemical: sensiron,scd30: Update maintainers field
This isn't a bug, but there's a typo (sensiron) in the subject line prefix.
It should be sensirion.
> Tomasz Duszynski is no longer the maintainer of the SCD30 driver.
> Replace his entry with mine.
Does this change also need to update the central MAINTAINERS file? The patch
only modifies the device tree bindings YAML file, leaving Tomasz Duszynski
still listed as the maintainer of the driver in the main MAINTAINERS file.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260510020758.233721-1-m32285159@gmail.com?part=1
next prev parent reply other threads:[~2026-05-11 11:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-10 2:07 [PATCH] dt-bindings: iio: chemical: sensiron,scd30: Update maintainers field Maxwell Doose
2026-05-11 11:35 ` sashiko-bot [this message]
2026-05-11 12:09 ` Jonathan Cameron
2026-05-11 13:10 ` 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=20260511113523.BC06BC2BCB0@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=m32285159@gmail.com \
--cc=robh@kernel.org \
--cc=sashiko@lists.linux.dev \
/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