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,
corbet@lwn.net, shuah@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kselftest@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH net-next v2 0/8] netconsole: Add taskname sysdata support
Date: Tue, 04 Mar 2025 14:50:33 +0000 [thread overview]
Message-ID: <174109983302.170664.16431215519500952572.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250228-netcons_current-v2-0-f53ff79a0db2@debian.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 28 Feb 2025 04:50:16 -0800 you wrote:
> This patchset introduces a new feature to the netconsole extradata
> subsystem that enables the inclusion of the current task's name in the
> sysdata output of netconsole messages.
>
> This enhancement is particularly valuable for large-scale deployments,
> such as Meta's, where netconsole collects messages from millions of
> servers and stores them in a data warehouse for analysis. Engineers
> often rely on these messages to investigate issues and assess kernel
> health.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/8] netconsole: prefix CPU_NR sysdata feature with SYSDATA_
https://git.kernel.org/netdev/net-next/c/8a683295c226
- [net-next,v2,2/8] netconsole: Make boolean comparison consistent
https://git.kernel.org/netdev/net-next/c/efb878fbe8d1
- [net-next,v2,3/8] netconsole: refactor CPU number formatting into separate function
https://git.kernel.org/netdev/net-next/c/4d989521a93b
- [net-next,v2,4/8] netconsole: add taskname to extradata entry count
https://git.kernel.org/netdev/net-next/c/33e4b29f2b3b
- [net-next,v2,5/8] netconsole: add configfs controls for taskname sysdata feature
https://git.kernel.org/netdev/net-next/c/09e877590bc2
- [net-next,v2,6/8] netconsole: add task name to extra data fields
https://git.kernel.org/netdev/net-next/c/dd30ae533242
- [net-next,v2,7/8] netconsole: docs: document the task name feature
https://git.kernel.org/netdev/net-next/c/7010b619830f
- [net-next,v2,8/8] netconsole: selftest: add task name append testing
https://git.kernel.org/netdev/net-next/c/d7a2522426e8
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:[~2025-03-04 14:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 12:50 [PATCH net-next v2 0/8] netconsole: Add taskname sysdata support Breno Leitao
2025-02-28 12:50 ` [PATCH net-next v2 1/8] netconsole: prefix CPU_NR sysdata feature with SYSDATA_ Breno Leitao
2025-02-28 12:50 ` [PATCH net-next v2 2/8] netconsole: Make boolean comparison consistent Breno Leitao
2025-03-04 11:50 ` Simon Horman
2025-02-28 12:50 ` [PATCH net-next v2 3/8] netconsole: refactor CPU number formatting into separate function Breno Leitao
2025-02-28 12:50 ` [PATCH net-next v2 4/8] netconsole: add taskname to extradata entry count Breno Leitao
2025-02-28 12:50 ` [PATCH net-next v2 5/8] netconsole: add configfs controls for taskname sysdata feature Breno Leitao
2025-02-28 12:50 ` [PATCH net-next v2 6/8] netconsole: add task name to extra data fields Breno Leitao
2025-03-04 11:52 ` Simon Horman
2025-02-28 12:50 ` [PATCH net-next v2 7/8] netconsole: docs: document the task name feature Breno Leitao
2025-02-28 12:50 ` [PATCH net-next v2 8/8] netconsole: selftest: add task name append testing Breno Leitao
2025-03-04 14: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=174109983302.170664.16431215519500952572.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=corbet@lwn.net \
--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-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@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;
as well as URLs for NNTP newsgroup(s).