From: patchwork-bot+netdevbpf@kernel.org
To: Chukun Pan <amadeus@jmu.edu.cn>
Cc: davem@davemloft.net, andrew@lunn.ch, pabeni@redhat.com,
kuba@kernel.org, edumazet@google.com, linux@armlinux.org.uk,
daniel@makrotopia.org, hkallweit1@gmail.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v3 1/1] net: phy: realtek: Add support for PHY LEDs on RTL8221B
Date: Tue, 05 May 2026 02:00:15 +0000 [thread overview]
Message-ID: <177794641554.1386640.11256426332704981497.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260501100002.755672-1-amadeus@jmu.edu.cn>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 1 May 2026 18:00:02 +0800 you wrote:
> Realtek RTL8221B Ethernet PHY supports three LED pins which are used to
> indicate link status and activity. Add netdev trigger support for them.
>
> Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
> ---
> Changes in v3:
> - In led_hw_control_set, reset the LED polarity to default.
> - Link to v2: https://lore.kernel.org/all/20260420100800.2435204-1-amadeus@jmu.edu.cn/
> Changes in v2:
> - Invert the LED polarity in led_brightness_set to achieve LED_ON.
> - Link to v1: https://lore.kernel.org/all/20260401100010.3079700-1-amadeus@jmu.edu.cn/
>
> [...]
Here is the summary with links:
- [v3,1/1] net: phy: realtek: Add support for PHY LEDs on RTL8221B
https://git.kernel.org/netdev/net-next/c/d3aae4d954f9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-05-05 2:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-01 10:00 [PATCH v3 1/1] net: phy: realtek: Add support for PHY LEDs on RTL8221B Chukun Pan
2026-05-01 12:36 ` Andrew Lunn
2026-05-05 2:00 ` patchwork-bot+netdevbpf [this message]
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=177794641554.1386640.11256426332704981497.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=amadeus@jmu.edu.cn \
--cc=andrew@lunn.ch \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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