Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@xxxxxxxxxx>:
On Thu, 10 Oct 2024 13:53:36 +0100 you wrote:
> Other than described in commit c94d1783136e ("dt-bindings: net: phy:
> Make LED active-low property common") the absence of the 'active-low'
> property means not to touch the polarity settings which are inherited
> from reset defaults, the bootloader or bootstrap configuration. Hence,
> in order to override a LED pin being active-high in case of the default,
> bootloader or bootstrap setting being active-low an additional property
> 'active-high' is required. Document that property and make it mutually
> exclusive to the existing 'active-low' property.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/5] dt-bindings: leds: add 'active-high' property
(no matching commit)
- [net-next,v2,2/5] net: phy: support 'active-high' property for PHY LEDs
https://git.kernel.org/netdev/net-next/c/a274465cc3be
- [net-next,v2,3/5] net: phy: aquantia: correctly describe LED polarity override
https://git.kernel.org/netdev/net-next/c/9d55e68b19f2
- [net-next,v2,4/5] net: phy: mxl-gpy: correctly describe LED polarity
https://git.kernel.org/netdev/net-next/c/eb89c79c1b8f
- [net-next,v2,5/5] net: phy: intel-xway: add support for PHY LEDs
https://git.kernel.org/netdev/net-next/c/1758af47b98c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
