Re: [net-next PATCH v4 00/13] leds: introduce new LED hw control APIs

From: patchwork-bot+netdevbpf
Date: Wed May 31 2023 - 05:10:59 EST


This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@xxxxxxxxxxxxx>:

On Mon, 29 May 2023 18:32:30 +0200 you wrote:
> Since this series is cross subsystem between LED and netdev,
> a stable branch was created to facilitate merging process.
> This is based on top of branch ib-leds-netdev-v6.5 present here [1]
> and rebased on top of net-next since the LED stable branch got merged.
> This is a continue of [2]. It was decided to take a more gradual
> approach to implement LEDs support for switch and phy starting with
> basic support and then implementing the hw control part when we have all
> the prereq done.
> [...]

Here is the summary with links:
- [net-next,v4,01/13] leds: add APIs for LEDs hw control
- [net-next,v4,02/13] leds: add API to get attached device for LED hw control
- [net-next,v4,03/13] Documentation: leds: leds-class: Document new Hardware driven LEDs APIs
- [net-next,v4,04/13] leds: trigger: netdev: refactor code setting device name
- [net-next,v4,05/13] leds: trigger: netdev: introduce check for possible hw control
- [net-next,v4,06/13] leds: trigger: netdev: add basic check for hw control support
- [net-next,v4,07/13] leds: trigger: netdev: reject interval store for hw_control
- [net-next,v4,08/13] leds: trigger: netdev: add support for LED hw control
- [net-next,v4,09/13] leds: trigger: netdev: validate configured netdev
- [net-next,v4,10/13] leds: trigger: netdev: init mode if hw control already active
- [net-next,v4,11/13] leds: trigger: netdev: expose netdev trigger modes in linux include
- [net-next,v4,12/13] net: dsa: qca8k: implement hw_control ops
- [net-next,v4,13/13] net: dsa: qca8k: add op to get ports netdev

You are awesome, thank you!
Deet-doot-dot, I am a bot.