From: patchwork-bot+netdevbpf@kernel.org
To: Joe Damato <joe@dama.to>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, michael.chan@broadcom.com,
pavan.chebbi@broadcom.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] bnxt_en: Fix SW USO padding
Date: Thu, 15 Oct 2026 14:20:04 +0000 [thread overview]
Message-ID: <179207400477.3459929.16206928663915388110.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261009215426.2377946-1-joe@dama.to>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 9 Oct 2026 14:54:22 -0700 you wrote:
> Greetings:
>
> As a followup to Eric's fix a51d233ccd48 ("bnxt_en: fix DMA mapping length
> for padded small packets") which fixes padding for normal TX, this series
> fixes padding for SW USO.
>
> There are two cases I try to address:
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] bnxt_en: Add helper to fill SW USO payload BDs
https://git.kernel.org/netdev/net-next/c/70f63dc60872
- [net-next,v2,2/2] bnxt_en: Pad short SW USO segments to BNXT_MIN_PKT_SIZE
https://git.kernel.org/netdev/net-next/c/b0f7f9c87817
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-10-15 14:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 21:54 Joe Damato
2026-10-09 21:54 ` [PATCH net-next v2 1/2] bnxt_en: Add helper to fill SW USO payload BDs Joe Damato
2026-10-09 21:54 ` [PATCH net-next v2 2/2] bnxt_en: Pad short SW USO segments to BNXT_MIN_PKT_SIZE Joe Damato
2026-10-10 22:55 ` netdev-bot+sashiko
2026-10-12 17:01 ` Joe Damato
2026-10-12 21:27 ` Joe Damato
2026-10-15 14: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=179207400477.3459929.16206928663915388110.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=joe@dama.to \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.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
all inboxes | Powered by JetHome®