From: patchwork-bot+netdevbpf@kernel.org
To: Leon Romanovsky <leon@kernel.org>
Cc: kuba@kernel.org, leonro@nvidia.com, steffen.klassert@secunet.com,
edumazet@google.com, jianbol@nvidia.com, paulb@nvidia.com,
raeds@nvidia.com, netdev@vger.kernel.org, pabeni@redhat.com,
saeedm@nvidia.com, davem@davemloft.net,
simon.horman@corigine.com
Subject: Re: [PATCH net 0/3] mlx5 IPsec fixes
Date: Thu, 03 Aug 2023 01:50:21 +0000 [thread overview]
Message-ID: <169102742127.3352.6090408254573105846.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1690803944.git.leonro@nvidia.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 31 Jul 2023 14:58:39 +0300 you wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> Hi,
>
> The following patches are combination of Jianbo's work on IPsec eswitch mode
> together with our internal review toward addition of TCP protocol selectors
> support to IPSec packet offload.
>
> [...]
Here is the summary with links:
- [net,1/3] net/mlx5: fs_core: Make find_closest_ft more generic
https://git.kernel.org/netdev/net/c/618d28a535a0
- [net,2/3] net/mlx5: fs_core: Skip the FTs in the same FS_TYPE_PRIO_CHAINS fs_prio
https://git.kernel.org/netdev/net/c/c635ca45a7a2
- [net,3/3] net/mlx5e: Set proper IPsec source port in L4 selector
https://git.kernel.org/netdev/net/c/62da08331f1a
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:[~2023-08-03 1:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 11:58 [PATCH net 0/3] mlx5 IPsec fixes Leon Romanovsky
2023-07-31 11:58 ` [PATCH net 1/3] net/mlx5: fs_core: Make find_closest_ft more generic Leon Romanovsky
2023-07-31 11:58 ` [PATCH net 2/3] net/mlx5: fs_core: Skip the FTs in the same FS_TYPE_PRIO_CHAINS fs_prio Leon Romanovsky
2023-07-31 11:58 ` [PATCH net 3/3] net/mlx5e: Set proper IPsec source port in L4 selector Leon Romanovsky
2023-08-03 1:50 ` 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=169102742127.3352.6090408254573105846.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jianbol@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paulb@nvidia.com \
--cc=raeds@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=simon.horman@corigine.com \
--cc=steffen.klassert@secunet.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.