From: sashiko-bot@kernel.org
To: "Paul Sajna" <sajattack@postmarketos.org>
Cc: linux-leds@vger.kernel.org, lee@kernel.org
Subject: Re: [PATCH v4 3/4] leds: aw2013: Use dev_err_probe
Date: Sun, 08 Nov 2026 21:52:33 +0000 [thread overview]
Message-ID: <sashiko-outbox-204094@kernel.org> (raw)
In-Reply-To: <20261108-aw2013-aw20xx-rename-v4-3-826529beeb52@postmarketos.org>
> Failure to use dev_err_probe() for regulator requests violates
> LED subsystem guidelines. (At least according to sashiko [1])
>
> The original driver didn't use it, but it's worth cleaning up
> while I'm here.
>
> [1]: https://github.com/sashiko-dev/sashiko/blob/main/third_party/prompts/kernel/subsystem/leds.md?plain=1#L71
>
> Reviewed-by: Griffin Kroah-Hartman <griffin@kroah.com>
> Reviewed-by: David Heidelberg <david@ixit.cz>
>
> Signed-off-by: Paul Sajna <sajattack@postmarketos.org>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261108-aw2013-aw20xx-rename-v4-0-826529beeb52@postmarketos.org?part=3
next prev parent reply other threads:[~2026-11-08 21:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 21:49 [PATCH v4 0/4] leds: aw2013: Add AW2027 support Paul Sajna
2026-11-08 21:49 ` [PATCH v4 1/4] dt-bindings: leds: aw2013: Add awinic,aw2027 compatible Paul Sajna
2026-11-08 21:51 ` sashiko-bot
2026-11-08 21:49 ` [PATCH v4 2/4] leds: aw2013: Add AW2027 support Paul Sajna
2026-11-08 21:51 ` Paul Sajna
2026-11-08 21:55 ` sashiko-bot
2026-11-08 21:49 ` [PATCH v4 3/4] leds: aw2013: Use dev_err_probe Paul Sajna
2026-11-08 21:52 ` sashiko-bot [this message]
2026-11-08 21:49 ` [PATCH v4 4/4] leds: aw2013: Move assignment of chip->num_leds Paul Sajna
2026-11-08 22:00 ` sashiko-bot
2026-11-08 22:06 ` Paul Sajna
2026-11-08 22:08 ` [PATCH v4 0/4] leds: aw2013: Add AW2027 support Paul Sajna
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-204094@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=lee@kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=sajattack@postmarketos.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