From: sashiko-bot@kernel.org
To: "Nora Schiffer" <nora.schiffer@ew.tq-group.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org,
linux-leds@vger.kernel.org, lee@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 5/7] leds: pca995x: add sysfs files for error reporting
Date: Wed, 02 Sep 2026 12:40:41 +0000 [thread overview]
Message-ID: <20260902124042.3663A1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <69f8e83950d4d0f7c1bf60fe2f4047cf9bee5f79.1788350618.git.nora.schiffer@ew.tq-group.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] The `has_errors_store` function uses `strcmp()` to perform an exact match on "clear\n", which incorrectly rejects valid sysfs writes that omit a trailing newline.
- [Low] The commit message description is not capitalized, violating subsystem guidelines.
--
commit 663ea7a7fd850dadfe05eb1aef14f297e78e15b5
Author: Nora Schiffer <nora.schiffer@ew.tq-group.com>
leds: pca995x: add sysfs files for error reporting
The PCA995x has builtin failure detection. Provide sysfs files for
individual LED status (reporting "okay", "short-circuit" or
"open-circuit") as well as a global "has_errors" flag. has_errors is
sticky and must be cleared by writing "clear" to the sysfs file.
> leds: pca995x: add sysfs files for error reporting
[Severity: Low]
This isn't a bug, but the commit message description starts with a lowercase
letter. The LED subsystem guidelines request capitalizing the description
after the subsystem prefix.
> diff --git a/drivers/leds/leds-pca995x.c b/drivers/leds/leds-pca995x.c
> index b069b93d39a54..2232b74528a53 100644
> --- a/drivers/leds/leds-pca995x.c
> +++ b/drivers/leds/leds-pca995x.c
[ ... ]
> +static ssize_t has_errors_store(struct device *dev, struct device_attribute *attr,
> + const char *buf, size_t count)
> +{
> + struct pca995x_chip *chip = i2c_get_clientdata(to_i2c_client(dev));
> + int ret;
> +
> + if (strcmp(buf, "clear\n"))
> + return -EINVAL;
[Severity: Medium]
Does this exact string match in has_errors_store() reject valid sysfs writes
that omit a trailing newline?
If userspace writes exactly the word clear without a newline
(for example, using echo -n clear > has_errors), strcmp will fail and return
-EINVAL. Using sysfs_streq() instead of strcmp() would transparently handle
the presence or absence of a trailing newline from sysfs inputs.
> +
> + ret = regmap_update_bits(chip->regmap, PCA995X_MODE2,
> + PCA995X_MODE2_CLRERR, PCA995X_MODE2_CLRERR);
> +
> + return ret ?: count;
> +}
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/6d3600f99c77c31166f0b6a5ccfb7f518b53c4c9.1788350618.git.nora.schiffer@ew.tq-group.com?part=5
next prev parent reply other threads:[~2026-09-02 12:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 12:22 [PATCH 1/7] dt-bindings: leds: pca995x: describe reset-gpios property Nora Schiffer
2026-09-02 12:22 ` [PATCH 2/7] dt-bindings: leds: pca995x: describe output-gain property Nora Schiffer
2026-09-02 12:31 ` sashiko-bot
2026-09-02 13:10 ` Nora Schiffer
2026-09-03 8:34 ` Lee Jones
2026-09-03 13:09 ` Krzysztof Kozlowski
2026-09-02 12:22 ` [PATCH 3/7] leds: pca995x: add support for reset GPIO Nora Schiffer
2026-09-02 12:41 ` sashiko-bot
2026-09-02 12:22 ` [PATCH 4/7] leds: pca995x: make output gain configurable Nora Schiffer
2026-09-02 12:35 ` sashiko-bot
2026-09-02 12:22 ` [PATCH 5/7] leds: pca995x: add sysfs files for error reporting Nora Schiffer
2026-09-02 12:40 ` sashiko-bot [this message]
2026-09-02 12:22 ` [PATCH 6/7] leds: pca995x: do not use full on LED mode Nora Schiffer
2026-09-02 12:39 ` sashiko-bot
2026-09-02 12:22 ` [PATCH 7/7] leds: pca995x: add support for group brightness control Nora Schiffer
2026-09-02 12:43 ` sashiko-bot
2026-09-02 12:37 ` [PATCH 1/7] dt-bindings: leds: pca995x: describe reset-gpios property sashiko-bot
2026-09-02 16:16 ` Lee Jones
2026-09-03 6:42 ` Nora Schiffer
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=20260902124042.3663A1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lee@kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=nora.schiffer@ew.tq-group.com \
--cc=robh@kernel.org \
--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