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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20230531104611.GC449117@google.com>
Date:   Wed, 31 May 2023 11:46:11 +0100
From:   Lee Jones <lee@...nel.org>
To:     patchwork-bot+netdevbpf@...nel.org
Cc:     Christian Marangi <ansuelsmth@...il.com>, pavel@....cz,
        corbet@....net, andrew@...n.ch, f.fainelli@...il.com,
        olteanv@...il.com, davem@...emloft.net, edumazet@...gle.com,
        kuba@...nel.org, pabeni@...hat.com, linux-leds@...r.kernel.org,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        netdev@...r.kernel.org
Subject: Re: [net-next PATCH v4 00/13] leds: introduce new LED hw control APIs

On Wed, 31 May 2023, patchwork-bot+netdevbpf@...nel.org wrote:

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

*sigh*
 
> 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
>     https://git.kernel.org/netdev/net-next/c/ed554d3f9451
>   - [net-next,v4,02/13] leds: add API to get attached device for LED hw control
>     https://git.kernel.org/netdev/net-next/c/052c38eb17e8
>   - [net-next,v4,03/13] Documentation: leds: leds-class: Document new Hardware driven LEDs APIs
>     https://git.kernel.org/netdev/net-next/c/8aa2fd7b6698
>   - [net-next,v4,04/13] leds: trigger: netdev: refactor code setting device name
>     https://git.kernel.org/netdev/net-next/c/28a6a2ef18ad
>   - [net-next,v4,05/13] leds: trigger: netdev: introduce check for possible hw control
>     https://git.kernel.org/netdev/net-next/c/4fd1b6d47a7a
>   - [net-next,v4,06/13] leds: trigger: netdev: add basic check for hw control support
>     https://git.kernel.org/netdev/net-next/c/6352f25f9fad
>   - [net-next,v4,07/13] leds: trigger: netdev: reject interval store for hw_control
>     https://git.kernel.org/netdev/net-next/c/c84c80c7388f
>   - [net-next,v4,08/13] leds: trigger: netdev: add support for LED hw control
>     https://git.kernel.org/netdev/net-next/c/7c145a34ba6e
>   - [net-next,v4,09/13] leds: trigger: netdev: validate configured netdev
>     https://git.kernel.org/netdev/net-next/c/33ec0b53beff
>   - [net-next,v4,10/13] leds: trigger: netdev: init mode if hw control already active
>     https://git.kernel.org/netdev/net-next/c/0316cc5629d1
>   - [net-next,v4,11/13] leds: trigger: netdev: expose netdev trigger modes in linux include
>     https://git.kernel.org/netdev/net-next/c/947acacab5ea
>   - [net-next,v4,12/13] net: dsa: qca8k: implement hw_control ops
>     https://git.kernel.org/netdev/net-next/c/e0256648c831
>   - [net-next,v4,13/13] net: dsa: qca8k: add op to get ports netdev
>     https://git.kernel.org/netdev/net-next/c/4f53c27f772e
> 
> You are awesome, thank you!
> -- 
> Deet-doot-dot, I am a bot.
> https://korg.docs.kernel.org/patchwork/pwbot.html
> 
> 

-- 
Lee Jones [李琼斯]