From: patchwork-bot+netdevbpf@kernel.org
To: Mike Marciniszyn <mike.marciniszyn@gmail.com>
Cc: alexanderduyck@fb.com, kuba@kernel.org, kernel-team@meta.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] eth fbnic: Add debugfs for mbx and tx/rx
Date: Sat, 31 Jan 2026 02:50:17 +0000 [thread overview]
Message-ID: <176982781785.3974876.3426939571454500276.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260127200644.11640-1-mike.marciniszyn@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 27 Jan 2026 15:06:42 -0500 you wrote:
> From: "Mike Marciniszyn (Meta)" <mike.marciniszyn@gmail.com>
>
> This patches adds debugfs read of the firmware mailbox tx/rx
> and of the tx/rx rings for each napi vector.
>
> Mike Marciniszyn (Meta) (2):
> eth fbnic: Add debugfs hooks for firmware mailbox
> eth fbnic: Add debugfs hooks for tx/rx rings
>
> [...]
Here is the summary with links:
- [net-next,1/2] eth fbnic: Add debugfs hooks for firmware mailbox
https://git.kernel.org/netdev/net-next/c/ac7b803c2dd5
- [net-next,2/2] eth fbnic: Add debugfs hooks for tx/rx rings
https://git.kernel.org/netdev/net-next/c/df04373b0dab
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-01-31 2:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 20:06 [PATCH net-next 0/2] eth fbnic: Add debugfs for mbx and tx/rx mike.marciniszyn
2026-01-27 20:06 ` [PATCH net-next 1/2] eth fbnic: Add debugfs hooks for firmware mailbox mike.marciniszyn
2026-01-27 20:06 ` [PATCH net-next 2/2] eth fbnic: Add debugfs hooks for tx/rx rings mike.marciniszyn
2026-01-31 2: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=176982781785.3974876.3426939571454500276.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexanderduyck@fb.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.marciniszyn@gmail.com \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox