From: patchwork-bot+netdevbpf@kernel.org
To: Furong Xu <0x1207@gmail.com>
Cc: netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, alexandre.torgue@foss.st.com,
joabreu@synopsys.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
mcoquelin.stm32@gmail.com, xfr@outlook.com
Subject: Re: [PATCH net-next v2] net: stmmac: TSO: Simplify the code flow of DMA descriptor allocations
Date: Sat, 04 Jan 2025 16:40:33 +0000 [thread overview]
Message-ID: <173600883331.2467289.14997468976709274364.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241220080726.1733837-1-0x1207@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 20 Dec 2024 16:07:26 +0800 you wrote:
> The TCP Segmentation Offload (TSO) engine is an optional function in
> DWMAC cores, it is implemented for dwmac4 and dwxgmac2 only, ancient
> dwmac100 and dwmac1000 are not supported by hardware. Current driver
> code checks priv->dma_cap.tsoen which is read from MAC_HW_Feature1
> register to determine if TSO is enabled in hardware configurations,
> if (!priv->dma_cap.tsoen) driver never sets NETIF_F_TSO for net_device.
>
> [...]
Here is the summary with links:
- [net-next,v2] net: stmmac: TSO: Simplify the code flow of DMA descriptor allocations
https://git.kernel.org/netdev/net-next/c/356939999438
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-01-04 16:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 8:07 [PATCH net-next v2] net: stmmac: TSO: Simplify the code flow of DMA descriptor allocations Furong Xu
2025-01-04 16:40 ` 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=173600883331.2467289.14997468976709274364.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=0x1207@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=xfr@outlook.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