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, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] net: dsa: motorcomm: Fix register rollback in LED setup
Date: Mon, 05 Oct 2026 23:30:13 +0000 [thread overview]
Message-ID: <179124301369.1937173.18327578726103515612.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260930141151.3973221-1-mmyangfl@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 30 Sep 2026 22:11:48 +0800 you wrote:
> The LED error path writes back a stale snapshot of the whole words taken
> before the class device registration, silently reverting LED2 state of
> sibling LED groups already registered and reachable from sysfs. Although
> the odds are very small, fix it by reverting this group's fields only
> for correctness.
>
> Fixes: 9af9a8168213 ("net: dsa: motorcomm: Add LED support")
> Signed-off-by: David Yang <mmyangfl@gmail.com>
>
> [...]
Here is the summary with links:
- [net-next,v2] net: dsa: motorcomm: Fix register rollback in LED setup
https://git.kernel.org/netdev/net-next/c/1a2dbdb6602a
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-10-05 23:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 14:11 [PATCH net-next v2] net: dsa: motorcomm: Fix register rollback in LED setup David Yang
2026-09-30 14:14 ` netdev-bot+sinfo
2026-09-30 20:08 ` David Yang
2026-10-05 23: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=179124301369.1937173.18327578726103515612.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.