From: Ross Cawston <ross@r-sc.ca>
To: markus.stockhausen@gmx.de, andrew@lunn.ch
Cc: lee@kernel.org, pavel@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
chris.packham@alliedtelesis.co.nz, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, Ross Cawston <ross@r-sc.ca>
Subject: Re: [PATCH 0/3] leds: add Realtek RTL9300 port LEDs under software control
Date: Mon, 19 Oct 2026 16:00:53 -0700 [thread overview]
Message-ID: <20261019230053.503-1-ross@r-sc.ca> (raw)
In-Reply-To: <010701dd5f94$d636ff70$82a4fe50$@gmx.de>
On Mon, Oct 19, 2026 at 08:41 AM +0200, Markus Stockhausen wrote:
> [...] it is currently beyond the time available.
Thanks Markus, that answers it.
Then please drop this series. The PoE LEDs of this board go to OpenWrt
with openwrt/openwrt#25341 for now, and I'll come back to the port LEDs,
in the port nodes, once there is an RTL930x switch driver upstream.
Ross
next prev parent reply other threads:[~2026-10-19 23:01 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
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 [this message]
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=20261019230053.503-1-ross@r-sc.ca \
--to=ross@r-sc.ca \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=markus.stockhausen@gmx.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavel@kernel.org \
--cc=robh@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.