From: patchwork-bot+netdevbpf@kernel.org
To: Lee Trager <lee@trager.us>
Cc: alexanderduyck@fb.com, kuba@kernel.org, kernel-team@meta.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, kees@kernel.org, gustavoars@kernel.org,
sanman.p211993@gmail.com, mohsin.bashr@gmail.com,
suhui@nfschina.com, vadim.fedorenko@linux.dev, horms@kernel.org,
kalesh-anakkur.purayil@broadcom.com, jacob.e.keller@intel.com,
andrew@lunn.ch, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH net-next 0/6] eth: fbnic: Add firmware logging support
Date: Wed, 09 Jul 2025 00:20:11 +0000 [thread overview]
Message-ID: <175202041127.172847.7768220901270765799.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250702192207.697368-1-lee@trager.us>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 2 Jul 2025 12:12:06 -0700 you wrote:
> Firmware running on fbnic generates device logs. These logs contain useful
> information about the device which may or may not be related to the host.
> Logs are stored in a ring buffer and accessible through DebugFS.
>
> Lee Trager (6):
> eth: fbnic: Fix incorrect minimum firmware version
> eth: fbnic: Use FIELD_PREP to generate minimum firmware version
> eth: fbnic: Create ring buffer for firmware logs
> eth: fbnic: Add mailbox support for firmware logs
> eth: fbnic: Enable firmware logging
> eth: fbnic: Create fw_log file in DebugFS
>
> [...]
Here is the summary with links:
- [net-next,1/6] eth: fbnic: Fix incorrect minimum firmware version
https://git.kernel.org/netdev/net-next/c/dd62e960a755
- [net-next,2/6] eth: fbnic: Use FIELD_PREP to generate minimum firmware version
https://git.kernel.org/netdev/net-next/c/e48f6620ee81
- [net-next,3/6] eth: fbnic: Create ring buffer for firmware logs
https://git.kernel.org/netdev/net-next/c/c2b93d6beca8
- [net-next,4/6] eth: fbnic: Add mailbox support for firmware logs
https://git.kernel.org/netdev/net-next/c/2e972f32ae5f
- [net-next,5/6] eth: fbnic: Enable firmware logging
https://git.kernel.org/netdev/net-next/c/ecc53b1b46c8
- [net-next,6/6] eth: fbnic: Create fw_log file in DebugFS
https://git.kernel.org/netdev/net-next/c/432407c86993
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-07-09 0:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 19:12 Lee Trager
2025-07-02 19:12 ` [PATCH net-next 1/6] eth: fbnic: Fix incorrect minimum firmware version Lee Trager
2025-07-02 19:12 ` [PATCH net-next 2/6] eth: fbnic: Use FIELD_PREP to generate " Lee Trager
2025-07-02 19:12 ` [PATCH net-next 3/6] eth: fbnic: Create ring buffer for firmware logs Lee Trager
2025-07-02 19:12 ` [PATCH net-next 4/6] eth: fbnic: Add mailbox support " Lee Trager
2025-07-02 19:12 ` [PATCH net-next 5/6] eth: fbnic: Enable firmware logging Lee Trager
2025-07-02 19:12 ` [PATCH net-next 6/6] eth: fbnic: Create fw_log file in DebugFS Lee Trager
2025-07-02 20:45 ` [PATCH net-next 0/6] eth: fbnic: Add firmware logging support Jacob Keller
2025-07-09 0: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=175202041127.172847.7768220901270765799.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexanderduyck@fb.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gustavoars@kernel.org \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=kees@kernel.org \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=lee@trager.us \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mohsin.bashr@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sanman.p211993@gmail.com \
--cc=suhui@nfschina.com \
--cc=vadim.fedorenko@linux.dev \
/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
all inboxes | Powered by JetHome®