From: patchwork-bot+netdevbpf@kernel.org
To: Aditya Garg <gargaditya@linux.microsoft.com>
Cc: kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
decui@microsoft.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
longli@microsoft.com, kotaranov@microsoft.com, horms@kernel.org,
shradhagupta@linux.microsoft.com, ssengar@linux.microsoft.com,
ernis@linux.microsoft.com, dipayanroy@linux.microsoft.com,
shirazsaleem@microsoft.com, leon@kernel.org, mlevitsk@redhat.com,
yury.norov@gmail.com, sbhatta@marvell.com,
linux-hyperv@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
gargaditya@microsoft.com
Subject: Re: [PATCH net-next v6 0/2] net: mana: Enforce TX SGE limit and fix error cleanup
Date: Thu, 20 Nov 2025 04:30:10 +0000 [thread overview]
Message-ID: <176361301025.1077848.8735410574086807354.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1763464269-10431-1-git-send-email-gargaditya@linux.microsoft.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 18 Nov 2025 03:11:07 -0800 you wrote:
> Add pre-transmission checks to block SKBs that exceed the hardware's SGE
> limit. Force software segmentation for GSO traffic and linearize non-GSO
> packets as needed.
>
> Update TX error handling to drop failed SKBs and unmap resources
> immediately.
>
> [...]
Here is the summary with links:
- [net-next,v6,1/2] net: mana: Handle SKB if TX SGEs exceed hardware limit
https://git.kernel.org/netdev/net-next/c/934fa943b537
- [net-next,v6,2/2] net: mana: Drop TX skb on post_work_request failure and unmap resources
https://git.kernel.org/netdev/net-next/c/45120304e841
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-11-20 4:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 11:11 [PATCH net-next v6 0/2] net: mana: Enforce TX SGE limit and fix error cleanup Aditya Garg
2025-11-18 11:11 ` [PATCH net-next v6 1/2] net: mana: Handle SKB if TX SGEs exceed hardware limit Aditya Garg
2025-11-18 11:11 ` [PATCH net-next v6 2/2] net: mana: Drop TX skb on post_work_request failure and unmap resources Aditya Garg
2025-11-20 4:30 ` 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=176361301025.1077848.8735410574086807354.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=dipayanroy@linux.microsoft.com \
--cc=edumazet@google.com \
--cc=ernis@linux.microsoft.com \
--cc=gargaditya@linux.microsoft.com \
--cc=gargaditya@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=horms@kernel.org \
--cc=kotaranov@microsoft.com \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=leon@kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=mlevitsk@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=shirazsaleem@microsoft.com \
--cc=shradhagupta@linux.microsoft.com \
--cc=ssengar@linux.microsoft.com \
--cc=wei.liu@kernel.org \
--cc=yury.norov@gmail.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.