From: Andrew Lunn <andrew@lunn.ch>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Christian Marangi <ansuelsmth@gmail.com>,
Pavel Machek <pavel@ucw.cz>, Lee Jones <lee@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
linux-leds@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [net-next PATCH v4 00/13] leds: introduce new LED hw control APIs
Date: Tue, 30 May 2023 14:54:16 +0200 [thread overview]
Message-ID: <7e5d1ed6-3fd7-4110-8171-9efd19b59023@lunn.ch> (raw)
In-Reply-To: <20230529221722.549dfbd8@kernel.org>
On Mon, May 29, 2023 at 10:17:22PM -0700, Jakub Kicinski wrote:
> 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?
From Christian and my side, yes. Ideally with Acked-by from Lee. We
have more patches to come, and we will just stack them on top in
net-next. The majority of those patches are for network drivers, not
the LED subsystem.
If there are going to be any merge conflicts, they will be to the core
LED header files. And such conflicts should be simple to resolve in
linux-next. If anybody else starts hacking on ledtrig-netdev.c then we
have problems, especially if it is an LED wide change. I don't know
how easy it is to create a stable branch from net-next, which could be
pulled into led-next, without it actually pulling in a huge number of
networking patches?
Lee?
Andrew
next prev parent reply other threads:[~2023-05-30 12:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 16:32 [net-next PATCH v4 00/13] leds: introduce new LED hw control APIs Christian Marangi
2023-05-29 16:32 ` [net-next PATCH v4 01/13] leds: add APIs for LEDs hw control Christian Marangi
2023-05-29 16:32 ` [net-next PATCH v4 02/13] leds: add API to get attached device for LED " Christian Marangi
2023-05-29 16:32 ` [net-next PATCH v4 03/13] Documentation: leds: leds-class: Document new Hardware driven LEDs APIs Christian Marangi
2023-05-29 17:07 ` Andrew Lunn
2023-05-29 16:32 ` [net-next PATCH v4 04/13] leds: trigger: netdev: refactor code setting device name Christian Marangi
2023-05-29 16:32 ` [net-next PATCH v4 05/13] leds: trigger: netdev: introduce check for possible hw control Christian Marangi
2023-05-29 16:32 ` [net-next PATCH v4 06/13] leds: trigger: netdev: add basic check for hw control support Christian Marangi
2023-05-29 16:32 ` [net-next PATCH v4 07/13] leds: trigger: netdev: reject interval store for hw_control Christian Marangi
2023-05-29 16:32 ` [net-next PATCH v4 08/13] leds: trigger: netdev: add support for LED hw control Christian Marangi
2023-05-29 16:32 ` [net-next PATCH v4 09/13] leds: trigger: netdev: validate configured netdev Christian Marangi
2023-05-29 16:32 ` [net-next PATCH v4 10/13] leds: trigger: netdev: init mode if hw control already active Christian Marangi
2023-05-29 16:32 ` [net-next PATCH v4 11/13] leds: trigger: netdev: expose netdev trigger modes in linux include Christian Marangi
2023-05-29 16:32 ` [net-next PATCH v4 12/13] net: dsa: qca8k: implement hw_control ops Christian Marangi
2023-05-29 16:32 ` [net-next PATCH v4 13/13] net: dsa: qca8k: add op to get ports netdev Christian Marangi
2023-05-30 5:17 ` [net-next PATCH v4 00/13] leds: introduce new LED hw control APIs Jakub Kicinski
2023-05-30 12:54 ` Andrew Lunn [this message]
2023-05-31 9:10 ` patchwork-bot+netdevbpf
2023-05-31 10:46 ` Lee Jones
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=7e5d1ed6-3fd7-4110-8171-9efd19b59023@lunn.ch \
--to=andrew@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=lee@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=pavel@ucw.cz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).