From: patchwork-bot+netdevbpf@kernel.org
To: Breno Leitao <leitao@debian.org>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@meta.com, stable@vger.kernel.org
Subject: Re: [PATCH net] netconsole: fix sysdata_release_enabled_show checking wrong flag
Date: Wed, 04 Mar 2026 01:50:07 +0000 [thread overview]
Message-ID: <177258900705.1554347.8845916164165638231.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260302-sysdata_release_fix-v1-1-e5090f677c7c@debian.org>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 02 Mar 2026 03:40:46 -0800 you wrote:
> sysdata_release_enabled_show() checks SYSDATA_TASKNAME instead of
> SYSDATA_RELEASE, causing the configfs release_enabled attribute to
> reflect the taskname feature state rather than the release feature
> state. This is a copy-paste error from the adjacent
> sysdata_taskname_enabled_show() function.
>
> The corresponding _store function already uses the correct
> SYSDATA_RELEASE flag.
>
> [...]
Here is the summary with links:
- [net] netconsole: fix sysdata_release_enabled_show checking wrong flag
https://git.kernel.org/netdev/net/c/5af6e8b54927
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-03-04 1:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 11:40 [PATCH net] netconsole: fix sysdata_release_enabled_show checking wrong flag Breno Leitao
2026-03-04 1:50 ` 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=177258900705.1554347.8845916164165638231.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.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 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.