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, pmladek@suse.com,
john.ogness@linutronix.de, gregkh@linuxfoundation.org,
rostedt@goodmis.org, senozhatsky@chromium.org,
akpm@linux-foundation.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, asantostc@gmail.com, efault@gmx.de,
gustavold@gmail.com, calvin@wbinvd.org, jv@jvosburgh.net,
mpdesouza@suse.com, kernel-team@meta.com, horms@kernel.org
Subject: Re: [PATCH net-next v7 0/4] net: netconsole: convert to NBCON console infrastructure
Date: Wed, 11 Feb 2026 04:20:15 +0000 [thread overview]
Message-ID: <177078361556.4190841.1165444988893621520.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260206-nbcon-v7-0-62bda69b1b41@debian.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 06 Feb 2026 04:45:28 -0800 you wrote:
> This series adds support for the nbcon (new buffer console) infrastructure
> to netconsole, enabling lock-free, priority-based console operations that
> are safer in crash scenarios.
>
> The implementation is introduced in three steps:
>
> 0) Extend printk to expose CPU and taskname (task->comm) where the
> printk originated from. (Thanks John and Petr for the support in
> getting this done)
> 1) Refactor the message fragmentation logic into a reusable helper function
> 2) Extend nbcon support to non-extended (basic) consoles using the same
> infrastructure.
>
> [...]
Here is the summary with links:
- [net-next,v7,1/4] printk: Add execution context (task name/CPU) to printk_info
https://git.kernel.org/netdev/net-next/c/60325c27d3cf
- [net-next,v7,2/4] netconsole: extract message fragmentation into send_msg_udp()
https://git.kernel.org/netdev/net-next/c/eaf35bc63be7
- [net-next,v7,3/4] netconsole: convert to NBCON console infrastructure
https://git.kernel.org/netdev/net-next/c/7eab73b18630
- [net-next,v7,4/4] netconsole: Use printk context for CPU and task information
https://git.kernel.org/netdev/net-next/c/79ba362b4337
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-02-11 4:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 12:45 [PATCH net-next v7 0/4] net: netconsole: convert to NBCON console infrastructure Breno Leitao
2026-02-06 12:45 ` [PATCH net-next v7 1/4] printk: Add execution context (task name/CPU) to printk_info Breno Leitao
2026-02-06 14:08 ` John Ogness
2026-02-12 15:28 ` Geert Uytterhoeven
2026-02-06 12:45 ` [PATCH net-next v7 2/4] netconsole: extract message fragmentation into send_msg_udp() Breno Leitao
2026-02-06 12:45 ` [PATCH net-next v7 3/4] netconsole: convert to NBCON console infrastructure Breno Leitao
2026-02-06 12:45 ` [PATCH net-next v7 4/4] netconsole: Use printk context for CPU and task information Breno Leitao
2026-02-11 4:20 ` 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=177078361556.4190841.1165444988893621520.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andrew+netdev@lunn.ch \
--cc=asantostc@gmail.com \
--cc=calvin@wbinvd.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=efault@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=gustavold@gmail.com \
--cc=horms@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=jv@jvosburgh.net \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpdesouza@suse.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.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