From: sashiko-bot@kernel.org
To: "Ross Cawston" <ross@r-sc.ca>
Cc: linux-leds@vger.kernel.org, lee@kernel.org
Subject: Re: [PATCH 2/3] dt-bindings: net: realtek,rtl9301-switch: add port LED controller
Date: Mon, 19 Oct 2026 20:04:56 +0000 [thread overview]
Message-ID: <sashiko-outbox-178159@kernel.org> (raw)
In-Reply-To: <20261018194339.132-3-ross@r-sc.ca>
> The switch drives the port LEDs, and some boards wire LEDs to it that
> have no hardware function and are switched in software, such as PoE
> status LEDs. Allow the software LED control block, described by
> realtek,rtl9301-port-leds, as a child of the switch like its I2C and
> MDIO controllers.
>
> Signed-off-by: Ross Cawston <ross@r-sc.ca>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261018194339.132-1-ross@r-sc.ca?part=2
next prev parent reply other threads:[~2026-10-19 20:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 19:43 [PATCH 0/3] leds: add Realtek RTL9300 port LEDs under software control Ross Cawston
2026-10-18 19:43 ` [PATCH 1/3] dt-bindings: leds: add Realtek RTL9301 port LEDs Ross Cawston
2026-10-19 20:04 ` sashiko-bot
2026-10-18 19:43 ` [PATCH 2/3] dt-bindings: net: realtek,rtl9301-switch: add port LED controller Ross Cawston
2026-10-19 20:04 ` sashiko-bot [this message]
2026-10-20 7:29 ` Krzysztof Kozlowski
2026-10-18 19:43 ` [PATCH 3/3] leds: add Realtek RTL9300 port LED driver Ross Cawston
2026-10-19 7:01 ` Uwe Kleine-König
2026-10-19 20:04 ` sashiko-bot
2026-10-18 22:36 ` [PATCH 0/3] leds: add Realtek RTL9300 port LEDs under software control Andrew Lunn
2026-10-18 23:20 ` Ross Cawston
2026-10-19 0:02 ` Andrew Lunn
2026-10-19 5:42 ` Ross Cawston
2026-10-19 6:41 ` AW: " Markus Stockhausen
2026-10-19 23:00 ` Ross Cawston
2026-10-20 20:16 ` Chris Packham
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-178159@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=lee@kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=ross@r-sc.ca \
--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