From: patchwork-bot+netdevbpf@kernel.org
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, horms@kernel.org,
kernel-team@meta.com, kuba@kernel.org, pabeni@redhat.com
Subject: Re: [net PATCH 0/6] fbnic: Follow-up fixes for the Tx idle check, HW stats and FW mailbox allocations
Date: Thu, 19 Nov 2026 23:50:09 +0000 [thread overview]
Message-ID: <179513220927.3927581.15064062874489023327.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <179460241885.8819.7179935130629202331.stgit@ahduyck-xeon-server.home.arpa>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 13 Nov 2026 12:41:19 -0800 you wrote:
> Follow-up fixes for fbnic on top of the series that was just applied
> to net, plus two fixes for FW mailbox allocations under memory pressure.
>
> Patch 1 makes the Tx idle check wait for in-flight PTP timestamps. The
> QM idle registers do not cover the TMI completion path, so they can
> report idle while a timestamp completion is still outstanding.
>
> [...]
Here is the summary with links:
- [net,1/6] fbnic: Wait for in-flight PTP timestamps before treating Tx as idle
(no matching commit)
- [net,2/6] fbnic: Do not accumulate HW stats from failed register reads
https://git.kernel.org/netdev/net-next/c/2d3c52a43b9d
- [net,3/6] fbnic: Cover all of the HW stats with the stats lock
(no matching commit)
- [net,4/6] fbnic: Initialize and reset the HW stats before they can be read
(no matching commit)
- [net,5/6] fbnic: Stamp heartbeat and ownership requests after allocating them
https://git.kernel.org/netdev/net-next/c/73694a4a031b
- [net,6/6] fbnic: Allocate FW completions with kvzalloc
https://git.kernel.org/netdev/net-next/c/3abdc3aa3390
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-11-19 23:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 20:41 [net PATCH 0/6] fbnic: Follow-up fixes for the Tx idle check, HW stats and FW mailbox allocations Alexander Duyck
2026-11-13 20:41 ` [net PATCH 1/6] fbnic: Wait for in-flight PTP timestamps before treating Tx as idle Alexander Duyck
2026-11-17 21:14 ` netdev-bot+sashiko
2026-11-17 21:31 ` Alexander Duyck
2026-11-19 23:33 ` Jakub Kicinski
2026-11-13 20:41 ` [net PATCH 2/6] fbnic: Do not accumulate HW stats from failed register reads Alexander Duyck
2026-11-17 21:14 ` netdev-bot+sashiko
2026-11-17 22:11 ` Alexander Duyck
2026-11-13 20:41 ` [net PATCH 3/6] fbnic: Cover all of the HW stats with the stats lock Alexander Duyck
2026-11-17 21:14 ` netdev-bot+sashiko
2026-11-17 22:01 ` Alexander Duyck
2026-11-13 20:41 ` [net PATCH 4/6] fbnic: Initialize and reset the HW stats before they can be read Alexander Duyck
2026-11-13 20:42 ` [net PATCH 5/6] fbnic: Stamp heartbeat and ownership requests after allocating them Alexander Duyck
2026-11-13 20:42 ` [net PATCH 6/6] fbnic: Allocate FW completions with kvzalloc Alexander Duyck
2026-11-19 23:49 ` [net PATCH 0/6] fbnic: Follow-up fixes for the Tx idle check, HW stats and FW mailbox allocations Jakub Kicinski
2026-11-19 23:50 ` patchwork-bot+netdevbpf
2026-11-19 23: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=179513220927.3927581.15064062874489023327.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexander.duyck@gmail.com \
--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=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 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.