From: patchwork-bot+netdevbpf@kernel.org
To: Saeed Mahameed <saeed@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, saeedm@nvidia.com, netdev@vger.kernel.org,
tariqt@nvidia.com, leonro@nvidia.com, phaddad@nvidia.com
Subject: Re: [net V3 01/15] net/mlx5e: Honor user choice of IPsec replay window size
Date: Fri, 08 Dec 2023 10:40:28 +0000 [thread overview]
Message-ID: <170203202800.16211.5959491781450485697.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231205214534.77771-2-saeed@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Saeed Mahameed <saeedm@nvidia.com>:
On Tue, 5 Dec 2023 13:45:20 -0800 you wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> Users can configure IPsec replay window size, but mlx5 driver didn't
> honor their choice and set always 32bits. Fix assignment logic to
> configure right size from the beginning.
>
> Fixes: 7db21ef4566e ("net/mlx5e: Set IPsec replay sequence numbers")
> Reviewed-by: Patrisious Haddad <phaddad@nvidia.com>
> Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
> Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
>
> [...]
Here is the summary with links:
- [net,V3,01/15] net/mlx5e: Honor user choice of IPsec replay window size
https://git.kernel.org/netdev/net/c/a5e400a985df
- [net,V3,02/15] net/mlx5e: Ensure that IPsec sequence packet number starts from 1
https://git.kernel.org/netdev/net/c/3d42c8cc67a8
- [net,V3,03/15] net/mlx5e: Unify esw and normal IPsec status table creation/destruction
https://git.kernel.org/netdev/net/c/94af50c0a9bb
- [net,V3,04/15] net/mlx5e: Remove exposure of IPsec RX flow steering struct
https://git.kernel.org/netdev/net/c/5ad00dee43b9
- [net,V3,05/15] net/mlx5e: Add IPsec and ASO syndromes check in HW
https://git.kernel.org/netdev/net/c/dddb49b63d86
- [net,V3,06/15] net/mlx5e: Tidy up IPsec NAT-T SA discovery
https://git.kernel.org/netdev/net/c/c2bf84f1d1a1
- [net,V3,07/15] net/mlx5e: Reduce eswitch mode_lock protection context
https://git.kernel.org/netdev/net/c/baac8351f74c
- [net,V3,08/15] net/mlx5e: Disable IPsec offload support if not FW steering
https://git.kernel.org/netdev/net/c/762a55a54eec
- [net,V3,09/15] net/mlx5e: Fix possible deadlock on mlx5e_tx_timeout_work
https://git.kernel.org/netdev/net/c/eab0da38912e
- [net,V3,10/15] net/mlx5e: TC, Don't offload post action rule if not supported
https://git.kernel.org/netdev/net/c/ccbe33003b10
- [net,V3,11/15] net/mlx5: Nack sync reset request when HotPlug is enabled
https://git.kernel.org/netdev/net/c/3d7a3f2612d7
- [net,V3,12/15] net/mlx5e: Check netdev pointer before checking its net ns
https://git.kernel.org/netdev/net/c/7aaf975238c4
- [net,V3,13/15] net/mlx5: Fix a NULL vs IS_ERR() check
https://git.kernel.org/netdev/net/c/ca4ef28d0ad8
- [net,V3,14/15] net/mlx5e: Correct snprintf truncation handling for fw_version buffer
(no matching commit)
- [net,V3,15/15] net/mlx5e: Correct snprintf truncation handling for fw_version buffer used by representors
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-12-08 10:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 21:45 [pull request][net V3 00/15] mlx5 fixes 2023-12-05 Saeed Mahameed
2023-12-05 21:45 ` [net V3 01/15] net/mlx5e: Honor user choice of IPsec replay window size Saeed Mahameed
2023-12-08 10:40 ` patchwork-bot+netdevbpf [this message]
2023-12-05 21:45 ` [net V3 02/15] net/mlx5e: Ensure that IPsec sequence packet number starts from 1 Saeed Mahameed
2023-12-05 21:45 ` [net V3 03/15] net/mlx5e: Unify esw and normal IPsec status table creation/destruction Saeed Mahameed
2023-12-05 21:45 ` [net V3 04/15] net/mlx5e: Remove exposure of IPsec RX flow steering struct Saeed Mahameed
2023-12-05 21:45 ` [net V3 05/15] net/mlx5e: Add IPsec and ASO syndromes check in HW Saeed Mahameed
2023-12-05 21:45 ` [net V3 06/15] net/mlx5e: Tidy up IPsec NAT-T SA discovery Saeed Mahameed
2023-12-05 21:45 ` [net V3 07/15] net/mlx5e: Reduce eswitch mode_lock protection context Saeed Mahameed
2023-12-05 21:45 ` [net V3 08/15] net/mlx5e: Disable IPsec offload support if not FW steering Saeed Mahameed
2023-12-05 21:45 ` [net V3 09/15] net/mlx5e: Fix possible deadlock on mlx5e_tx_timeout_work Saeed Mahameed
2023-12-05 21:45 ` [net V3 10/15] net/mlx5e: TC, Don't offload post action rule if not supported Saeed Mahameed
2023-12-05 21:45 ` [net V3 11/15] net/mlx5: Nack sync reset request when HotPlug is enabled Saeed Mahameed
2023-12-05 21:45 ` [net V3 12/15] net/mlx5e: Check netdev pointer before checking its net ns Saeed Mahameed
2023-12-05 21:45 ` [net V3 13/15] net/mlx5: Fix a NULL vs IS_ERR() check Saeed Mahameed
2023-12-05 21:45 ` [net V3 14/15] net/mlx5e: Correct snprintf truncation handling for fw_version buffer Saeed Mahameed
2023-12-05 21:45 ` [net V3 15/15] net/mlx5e: Correct snprintf truncation handling for fw_version buffer used by representors Saeed Mahameed
2023-12-05 22:48 ` [pull request][net V3 00/15] mlx5 fixes 2023-12-05 Jakub Kicinski
2023-12-06 20:58 ` Saeed Mahameed
2023-12-07 2:41 ` Jakub Kicinski
2023-12-07 19:03 ` Saeed Mahameed
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=170203202800.16211.5959491781450485697.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=phaddad@nvidia.com \
--cc=saeed@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).