From: patchwork-bot+netdevbpf@kernel.org
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: pavel@ucw.cz, lee@kernel.org, corbet@lwn.net, andrew@lunn.ch,
f.fainelli@gmail.com, olteanv@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, 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: Wed, 31 May 2023 09:10:26 +0000 [thread overview]
Message-ID: <168552422621.12579.18364898651664418572.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230529163243.9555-1-ansuelsmth@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
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
next prev parent reply other threads:[~2023-05-31 9:10 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
2023-05-31 9:10 ` patchwork-bot+netdevbpf [this message]
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=168552422621.12579.18364898651664418572.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=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).