From: patchwork-bot+netdevbpf@kernel.org
To: Tariq Toukan <tariqt@nvidia.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, netdev@vger.kernel.org, pabeni@redhat.com,
dtatulea@nvidia.com, eranbe@nvidia.com, gal@nvidia.com,
jianbol@nvidia.com, leon@kernel.org,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
mbloch@nvidia.com, moshe@nvidia.com, saeedm@nvidia.com,
shshitrit@nvidia.com, ychemla@nvidia.com
Subject: Re: [PATCH net 0/3] net/mlx5e: RS FEC variant fixes
Date: Sat, 05 Sep 2026 20:20:18 +0000 [thread overview]
Message-ID: <178863961888.1343052.2330784257627019651.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260902164634.3657606-1-tariqt@nvidia.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 2 Sep 2026 19:46:31 +0300 you wrote:
> Hi,
>
> This series by Shahar fixes three related bugs in the RS FEC handling
> for mlx5e, all stemming from incomplete coverage of the three RS FEC
> hardware variants: RS_528_514 (bit 2), RS_544_514_INTERLEAVED_QUAD
> (bit 4), and RS_544_514 (bit 7).
>
> [...]
Here is the summary with links:
- [net,1/3] net/mlx5e: Fix missing FEC mode mapping for RS_544_514_INTERLEAVED_QUAD
https://git.kernel.org/netdev/net/c/802eedcc0b25
- [net,2/3] net/mlx5e: Fix setting RS FEC after remapping
https://git.kernel.org/netdev/net/c/b9d755c5a375
- [net,3/3] net/mlx5e: Fix reporting support for all RS FEC variants
https://git.kernel.org/netdev/net/c/c84ce45a7a3f
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-05 20:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 16:46 Tariq Toukan
2026-09-02 16:46 ` [PATCH net 1/3] net/mlx5e: Fix missing FEC mode mapping for RS_544_514_INTERLEAVED_QUAD Tariq Toukan
2026-09-02 16:46 ` [PATCH net 2/3] net/mlx5e: Fix setting RS FEC after remapping Tariq Toukan
2026-09-02 16:46 ` [PATCH net 3/3] net/mlx5e: Fix reporting support for all RS FEC variants Tariq Toukan
2026-09-05 20: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=178863961888.1343052.2330784257627019651.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=eranbe@nvidia.com \
--cc=gal@nvidia.com \
--cc=jianbol@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=shshitrit@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=ychemla@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 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®