From: sashiko-bot@kernel.org
To: "Daniel Balint" <dbalint@google.com>
Cc: mfd@lists.linux.dev, lee@kernel.org
Subject: Re: [PATCH v1 3/3] mfd: cros_ec: load cros_ec_pwrmon on supported ECs
Date: Fri, 06 Nov 2026 19:36:32 +0000 [thread overview]
Message-ID: <sashiko-outbox-202156@kernel.org> (raw)
In-Reply-To: <20261106193129.43493-4-dbalint@google.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] mfd: cros_ec: lowercase description in commit subject
--
commit 9d3435eb48d0511f2f3d3ec653ce62f525f2879e
Author: Daniel Balint <dbalint@google.com>
mfd: cros_ec: load cros_ec_pwrmon on supported ECs
This commit registers the cros-ec-pwrmon MFD cell when the ChromeOS EC
advertises EC_FEATURE_PWRMON.
> mfd: cros_ec: load cros_ec_pwrmon on supported ECs
[Severity: Low]
This isn't a bug, but MFD commit subjects capitalize the description after
the prefix ("mfd: cros_ec: Load cros_ec_pwrmon on supported ECs").
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261106193129.43493-1-dbalint@google.com?part=3
next prev parent reply other threads:[~2026-11-06 19:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 19:31 [PATCH v1 0/3] Introduce cros_ec power monitoring Daniel Balint
2026-11-06 19:31 ` [PATCH v1 1/3] platform/chrome: cros_ec: fix alignment of ec_params_pwrmon Daniel Balint
2026-11-06 19:37 ` sashiko-bot
2026-11-07 23:53 ` Benson Leung
2026-11-06 19:31 ` [PATCH v1 2/3] iio: adc: add cros_ec_pwrmon driver Daniel Balint
2026-11-06 19:49 ` sashiko-bot
2026-11-07 1:25 ` Jonathan Cameron
2026-11-06 19:31 ` [PATCH v1 3/3] mfd: cros_ec: load cros_ec_pwrmon on supported ECs Daniel Balint
2026-11-06 19:36 ` sashiko-bot [this message]
2026-11-07 1:03 ` [PATCH v1 0/3] Introduce cros_ec power monitoring Jonathan Cameron
2026-11-09 2:05 ` (subset) " Tzung-Bi Shih
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=sashiko-outbox-202156@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dbalint@google.com \
--cc=lee@kernel.org \
--cc=mfd@lists.linux.dev \
--cc=sashiko-reviews@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;
as well as URLs for NNTP newsgroup(s).