From: patchwork-bot+netdevbpf@kernel.org
To: Donggeun Yoo <donggeunyoo.kernel@gmail.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
linux@armlinux.org.uk, daniel@makrotopia.org,
o.rempel@pengutronix.de, netdev@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3 0/3] net: phy: handle the active-high LED polarity mode
Date: Thu, 10 Sep 2026 15:50:08 +0000 [thread overview]
Message-ID: <178905540837.1510486.3215302337759175412.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260908105959.70453-1-donggeunyoo.kernel@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 8 Sep 2026 19:59:56 +0900 you wrote:
> Commit a274465cc3be ("net: phy: support 'active-high' property for PHY
> LEDs") let a device tree LED node request PHY_LED_ACTIVE_HIGH, but a
> ->led_polarity_set() that only handles PHY_LED_ACTIVE_LOW returns -EINVAL
> for it. of_phy_leds() propagates that, phy_probe() fails, the mdio device
> is left unbound, and phy_attach_direct() falls back to the genphy driver,
> so the PHY loses its driver-specific configuration. Three in-tree drivers
> still have that gap; each already programs active high as its default, so
> the fix is one case label per driver.
>
> [...]
Here is the summary with links:
- [net,v3,1/3] net: phy: dp83867: handle the active-high LED polarity mode
(no matching commit)
- [net,v3,2/3] net: phy: dp83td510: handle the active-high LED polarity mode
https://git.kernel.org/netdev/net/c/6ca81bbc31cd
- [net,v3,3/3] net: phy: qca808x: handle the active-high LED polarity mode
(no matching commit)
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-09-10 15:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 10:59 [PATCH net v3 0/3] net: phy: handle the active-high LED polarity mode Donggeun Yoo
2026-09-08 10:59 ` [PATCH net v3 1/3] net: phy: dp83867: " Donggeun Yoo
2026-09-08 14:02 ` Andrew Lunn
2026-09-08 10:59 ` [PATCH net v3 2/3] net: phy: dp83td510: " Donggeun Yoo
2026-09-08 14:06 ` Andrew Lunn
2026-09-08 10:59 ` [PATCH net v3 3/3] net: phy: qca808x: " Donggeun Yoo
2026-09-08 14:09 ` Andrew Lunn
2026-09-09 23:02 ` netdev-bot+sashiko
2026-09-10 15:20 ` [PATCH net v3 0/3] net: phy: " patchwork-bot+netdevbpf
2026-09-10 15:50 ` 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=178905540837.1510486.3215302337759175412.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=donggeunyoo.kernel@gmail.com \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--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 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.