From: patchwork-bot+netdevbpf@kernel.org
To: David Yang <mmyangfl@gmail.com>
Cc: netdev@vger.kernel.org, andrew@lunn.ch, olteanv@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v11 0/5] net: dsa: motorcomm: Add LED support
Date: Thu, 03 Sep 2026 03:30:14 +0000 [thread overview]
Message-ID: <178840621439.3072235.8474333977107368724.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260831044818.4103477-1-mmyangfl@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 31 Aug 2026 12:38:53 +0800 you wrote:
> LEDs can be described in the device tree using the standard LED node
> notation. Currently, only parallel mode and strict 1:1 mapping (i.e. the
> HW default) are supported.
>
> v10: https://lore.kernel.org/r/20260816193905.218112-1-mmyangfl@gmail.com
> - new patch to fix lock status check
> - LED control block redesigned
> v9: https://lore.kernel.org/r/20260726162731.1005803-1-mmyangfl@gmail.com
> - LED initialization sequence adjusted
> - add DT description
> v8: https://lore.kernel.org/r/20260725045008.858692-1-mmyangfl@gmail.com
> - limit the led port number
> v7: https://lore.kernel.org/r/20260723195335.806002-1-mmyangfl@gmail.com
> - rebase
> v6: https://lore.kernel.org/r/20260709014812.1158178-1-mmyangfl@gmail.com
> - per-port initialization support
> v5: https://lore.kernel.org/r/20260707064752.1030345-1-mmyangfl@gmail.com
> - improve trigger selection
> v4: https://lore.kernel.org/r/20260703165241.542195-1-mmyangfl@gmail.com
> - fix some reg op typos
> v3: https://lore.kernel.org/r/20260701155519.273212-1-mmyangfl@gmail.com
> - fix null pointer dereference
> - support polarity auto-configuration
> v2: https://lore.kernel.org/r/20260629183137.541341-1-mmyangfl@gmail.com
> - allocate LED structures only
> - eliminate double locking
> v1: https://lore.kernel.org/r/20260618202716.2166450-1-mmyangfl@gmail.com
> - set up polarity correctly
> - do not set up .brightness_get() to prevent dead lo
>
> [...]
Here is the summary with links:
- [net-next,v11,1/5] net: dsa: yt921x: Check lock status with lockdep_assert_held_once()
https://git.kernel.org/netdev/net-next/c/b1950d0426aa
- [net-next,v11,2/5] net: dsa: motorcomm: Move to subdirectory
https://git.kernel.org/netdev/net-next/c/9c472a0d7c38
- [net-next,v11,3/5] net: dsa: motorcomm: Split SMI module
https://git.kernel.org/netdev/net-next/c/e9423a64d382
- [net-next,v11,4/5] net: dsa: motorcomm: Add LED support
https://git.kernel.org/netdev/net-next/c/9af9a8168213
- [net-next,v11,5/5] dt-bindings: net: dsa: yt921x: Add LEDs definition example
https://git.kernel.org/netdev/net-next/c/5f28f63c5d19
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-03 3:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 4:38 [PATCH net-next v11 0/5] net: dsa: motorcomm: Add LED support David Yang
2026-08-31 4:38 ` [PATCH net-next v11 1/5] net: dsa: yt921x: Check lock status with lockdep_assert_held_once() David Yang
2026-08-31 23:29 ` Andrew Lunn
2026-09-02 0:56 ` Jakub Kicinski
2026-08-31 4:38 ` [PATCH net-next v11 2/5] net: dsa: motorcomm: Move to subdirectory David Yang
2026-08-31 4:38 ` [PATCH net-next v11 3/5] net: dsa: motorcomm: Split SMI module David Yang
2026-08-31 4:38 ` [PATCH net-next v11 4/5] net: dsa: motorcomm: Add LED support David Yang
2026-09-01 4:49 ` sashiko-bot
2026-09-02 0:56 ` Jakub Kicinski
2026-09-02 3:04 ` David Yang
2026-09-02 12:04 ` Andrew Lunn
2026-08-31 4:38 ` [PATCH net-next v11 5/5] dt-bindings: net: dsa: yt921x: Add LEDs definition example David Yang
2026-09-03 3:30 ` patchwork-bot+netdevbpf [this message]
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=178840621439.3072235.8474333977107368724.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmyangfl@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
/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