From: patchwork-bot+netdevbpf@kernel.org
To: Dimitri Daskalakis <dimitri.daskalakis1@gmail.com>
Cc: davem@davemloft.net, saeedm@nvidia.com, tariqt@nvidia.com,
mbloch@nvidia.com, leon@kernel.org, andrew+netdev@lunn.ch,
edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com,
gal@nvidia.com, cratiu@nvidia.com, dtatulea@nvidia.com,
noren@nvidia.com, cjubran@nvidia.com, bjorn@kernel.org,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: Re: [PATCH net-next v4] net/mlx5e: advertise tcp-data-split support
Date: Thu, 19 Nov 2026 00:10:19 +0000 [thread overview]
Message-ID: <179504701903.2637749.7879620797013573164.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261111170558.1654691-1-dimitri.daskalakis1@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 11 Nov 2026 09:05:58 -0800 you wrote:
> From: Dimitri Daskalakis <daskald@meta.com>
>
> Since commit 46bcce5dfd33 ("net/mlx5e: Support ethtool tcp-data-split
> settings"), mlx5 no longer reports tcp-data-split from
> mlx5e_ethtool_get_ringparam() and the reply carries only the stored
> config. With the default config (auto) the attribute is omitted, so the
> device looks like it does not support tcp-data-split, even while HW-GRO
> is on and SHAMPO is splitting headers.
>
> [...]
Here is the summary with links:
- [net-next,v4] net/mlx5e: advertise tcp-data-split support
https://git.kernel.org/netdev/net-next/c/db368b0d1fc4
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 0:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 17:05 [PATCH net-next v4] net/mlx5e: advertise tcp-data-split support Dimitri Daskalakis
2026-11-12 17:06 ` sashiko-bot
2026-11-12 17:45 ` Dimitri Daskalakis
2026-11-13 8:06 ` netdev-bot+sashiko
2026-11-13 17:59 ` Dimitri Daskalakis
2026-11-15 10:39 ` Nimrod Oren
2026-11-15 20:59 ` Dimitri Daskalakis
2026-11-17 17:49 ` Nimrod Oren
2026-11-18 10:58 ` Tariq Toukan
2026-11-19 0:10 ` 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=179504701903.2637749.7879620797013573164.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bjorn@kernel.org \
--cc=cjubran@nvidia.com \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=dimitri.daskalakis1@gmail.com \
--cc=dtatulea@nvidia.com \
--cc=edumazet@kernel.org \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=noren@nvidia.com \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.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.