All of lore.kernel.org
 help / color / mirror / Atom feed
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, jiri@nvidia.com, leonro@nvidia.com
Subject: Re: [PATCH net-next V4 0/8] {devlink,mlx5}: Add port function attributes for ipsec
Date: Mon, 28 Aug 2023 01:10:31 +0000	[thread overview]
Message-ID: <169318503178.15537.10958349208856861902.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230825062836.103744-1-saeed@kernel.org>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 24 Aug 2023 23:28:28 -0700 you wrote:
> From: Saeed Mahameed <saeedm@nvidia.com>
> 
> v4:
>  - Rebased on top of latest mlx5 changes, align with new code, fix build
>    warnings
> 
> v3:
>  - Changed newly introduced IPsec blocking routine
>    and as an outcome of testing already existing one.
>    I'm sending them together to avoid merge conflicts.
>  - Refactored patches to separate IFC part
>  - Simplified
> v2: https://lore.kernel.org/netdev/20230421104901.897946-1-dchumak@nvidia.com/
>  - Improve docs of ipsec_crypto vs ipsec_packet devlink attributes
>  - also see patches 2,4 for the changelog.
> 
> [...]

Here is the summary with links:
  - [net-next,V4,1/8] devlink: Expose port function commands to control IPsec crypto offloads
    https://git.kernel.org/netdev/net-next/c/62b6442c58dc
  - [net-next,V4,2/8] devlink: Expose port function commands to control IPsec packet offloads
    https://git.kernel.org/netdev/net-next/c/390a24cbc396
  - [net-next,V4,3/8] net/mlx5: Drop extra layer of locks in IPsec
    https://git.kernel.org/netdev/net-next/c/c46fb77383a6
  - [net-next,V4,4/8] net/mlx5e: Rewrite IPsec vs. TC block interface
    https://git.kernel.org/netdev/net-next/c/e25373416678
  - [net-next,V4,5/8] net/mlx5: Add IFC bits to support IPsec enable/disable
    https://git.kernel.org/netdev/net-next/c/17c8da5a3423
  - [net-next,V4,6/8] net/mlx5: Provide an interface to block change of IPsec capabilities
    https://git.kernel.org/netdev/net-next/c/8efd7b17a3b0
  - [net-next,V4,7/8] net/mlx5: Implement devlink port function cmds to control ipsec_crypto
    https://git.kernel.org/netdev/net-next/c/06bab69658a8
  - [net-next,V4,8/8] net/mlx5: Implement devlink port function cmds to control ipsec_packet
    https://git.kernel.org/netdev/net-next/c/b691b1116e82

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-08-28  1:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25  6:28 [PATCH net-next V4 0/8] {devlink,mlx5}: Add port function attributes for ipsec Saeed Mahameed
2023-08-25  6:28 ` [PATCH net-next V4 1/8] devlink: Expose port function commands to control IPsec crypto offloads Saeed Mahameed
2023-08-25  7:15   ` Jiri Pirko
2023-08-25  6:28 ` [PATCH net-next V4 2/8] devlink: Expose port function commands to control IPsec packet offloads Saeed Mahameed
2023-08-25  7:16   ` Jiri Pirko
2023-08-25  6:28 ` [PATCH net-next V4 3/8] net/mlx5: Drop extra layer of locks in IPsec Saeed Mahameed
2023-08-25  6:28 ` [PATCH net-next V4 4/8] net/mlx5e: Rewrite IPsec vs. TC block interface Saeed Mahameed
2023-08-25  6:28 ` [PATCH net-next V4 5/8] net/mlx5: Add IFC bits to support IPsec enable/disable Saeed Mahameed
2023-08-25  6:28 ` [PATCH net-next V4 6/8] net/mlx5: Provide an interface to block change of IPsec capabilities Saeed Mahameed
2023-08-25  6:28 ` [PATCH net-next V4 7/8] net/mlx5: Implement devlink port function cmds to control ipsec_crypto Saeed Mahameed
2023-08-25  6:28 ` [PATCH net-next V4 8/8] net/mlx5: Implement devlink port function cmds to control ipsec_packet Saeed Mahameed
2023-08-28  1: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=169318503178.15537.10958349208856861902.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jiri@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=leonro@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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 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.