From: patchwork-bot+netdevbpf@kernel.org
To: Danesh Petigara <danesh.petigara@broadcom.com>
Cc: justin.chen@broadcom.com, florian.fainelli@broadcom.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
bcm-kernel-feedback-list@broadcom.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/2] net: bcmasp: fix TX ring accounting bugs
Date: Fri, 04 Sep 2026 00:00:09 +0000 [thread overview]
Message-ID: <178848000914.4077563.14627683271472464588.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260831184235.4133351-1-danesh.petigara@broadcom.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 31 Aug 2026 11:42:33 -0700 you wrote:
> Two fixes for TX descriptor ring handling in the bcmasp driver:
>
> - tx_spb_ring_full() re-initialized next_index from
> intf->tx_spb_index on every loop iteration instead of advancing
> it, so it only ever checked a single descriptor slot regardless
> of cnt. This let bcmasp_xmit() proceed even when the ring didn't
> actually have enough free slots for the SKB's fragments.
>
> [...]
Here is the summary with links:
- [net,1/2] net: bcmasp: clear txcb->last before writing each descriptor
https://git.kernel.org/netdev/net/c/18e5e0ec0e92
- [net,2/2] net: bcmasp: fix tx_spb_ring_full() checking same slot cnt times
https://git.kernel.org/netdev/net/c/0c5cf62e72d7
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-09-04 0:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 18:42 [PATCH net 0/2] net: bcmasp: fix TX ring accounting bugs Danesh Petigara
2026-08-31 18:42 ` [PATCH net 1/2] net: bcmasp: clear txcb->last before writing each descriptor Danesh Petigara
2026-09-03 22:39 ` Florian Fainelli
2026-08-31 18:42 ` [PATCH net 2/2] net: bcmasp: fix tx_spb_ring_full() checking same slot cnt times Danesh Petigara
2026-09-03 22:39 ` Florian Fainelli
2026-09-04 0:00 ` 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=178848000914.4077563.14627683271472464588.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=danesh.petigara@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=horms@kernel.org \
--cc=justin.chen@broadcom.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox