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
| ||
|
Message-ID: <20230529221722.549dfbd8@kernel.org> Date: Mon, 29 May 2023 22:17:22 -0700 From: Jakub Kicinski <kuba@...nel.org> To: Christian Marangi <ansuelsmth@...il.com> Cc: Pavel Machek <pavel@....cz>, Lee Jones <lee@...nel.org>, Jonathan Corbet <corbet@....net>, Andrew Lunn <andrew@...n.ch>, Florian Fainelli <f.fainelli@...il.com>, Vladimir Oltean <olteanv@...il.com>, "David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <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 Mon, 29 May 2023 18:32:30 +0200 Christian Marangi 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. > > This is the main part of the series, the one that actually implement the > hw control API. Just to be 100% sure - these go into netdev/net-next directly, right? No stable branch needed?
Powered by blists - more mailing lists