All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Paolo Abeni <pabeni@redhat.com>, Jakub Kicinski <kuba@kernel.org>,
	"David S . Miller" <davem@davemloft.net>,
	Saeed Mahameed <saeedm@nvidia.com>,
	linux-netdev <netdev@vger.kernel.org>,
	RDMA mailing list <linux-rdma@vger.kernel.org>,
	Leon Romanovsky <leonro@nvidia.com>
Subject: Re: [GIT PULL] Please pull mlx5-next changes
Date: Tue, 12 Apr 2022 10:57:15 -0300	[thread overview]
Message-ID: <20220412135715.GA204876@nvidia.com> (raw)
In-Reply-To: <20220409055303.1223644-1-leon@kernel.org>

On Sat, Apr 09, 2022 at 08:53:03AM +0300, Leon Romanovsky wrote:
> The following changes since commit 3123109284176b1532874591f7c81f3837bbdc17:
> 
>   Linux 5.18-rc1 (2022-04-03 14:08:21 -0700)
> 
> are available in the Git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux.git mlx5-next
> 
> for you to fetch changes up to 2984287c4c19949d7eb451dcad0bd5c54a2a376f:
> 
> net/mlx5: Remove not-implemented IPsec capabilities (2022-04-09 08:25:07 +0300)
> ----------------------------------------------------------------
> Mellanox shared branch that includes:
>  * Removal of FPGA TLS code https://lore.kernel.org/all/cover.1649073691.git.leonro@nvidia.com
> 
>   Mellanox INNOVA TLS cards are EOL in May, 2018 [1]. As such, the code
>   is unmaintained, untested and not in-use by any upstream/distro oriented
>   customers. In order to reduce code complexity, drop the kernel code,
>   clean build config options and delete useless kTLS vs. TLS separation.
> 
>   [1] https://network.nvidia.com/related-docs/eol/LCR-000286.pdf
> 
>  * Removal of FPGA IPsec code https://lore.kernel.org/all/cover.1649232994.git.leonro@nvidia.com
> 
>   Together with FPGA TLS, the IPsec went to EOL state in the November of
>   2019 [1]. Exactly like FPGA TLS, no active customers exist for this
>   upstream code and all the complexity around that area can be deleted.
> 
>   [2] https://network.nvidia.com/related-docs/eol/LCR-000535.pdf
>    
>  * Fix to undefined behavior from Borislav https://lore.kernel.org/all/20220405151517.29753-11-bp@alien8.de
> 
> Signed-of-by: Leon Romanovsky <leonro@nvidia.com>
> ----------------------------------------------------------------
> Borislav Petkov (1):
>       IB/mlx5: Fix undefined behavior due to shift overflowing the constant
> 
> Leon Romanovsky (22):
>       net/mlx5_fpga: Drop INNOVA TLS support
>       net/mlx5: Reliably return TLS device capabilities
>       net/mlx5: Remove indirection in TLS build
>       net/mlx5: Remove tls vs. ktls separation as it is the same
>       net/mlx5: Cleanup kTLS function names and their exposure
>       net/mlx5_fpga: Drop INNOVA IPsec support
>       net/mlx5: Delete metadata handling logic
>       net/mlx5: Remove not-used IDA field from IPsec struct
>       net/mlx5: Remove XFRM no_trailer flag
>       net/mlx5: Remove FPGA ipsec specific statistics
>       RDMA/mlx5: Delete never supported IPsec flow action
>       RDMA/mlx5: Drop crypto flow steering API
>       RDMA/core: Delete IPsec flow action logic from the core
>       net/mlx5: Remove ipsec vs. ipsec offload file separation
>       net/mlx5: Remove useless IPsec device checks
>       net/mlx5: Unify device IPsec capabilities check
>       net/mlx5: Align flow steering allocation namespace to common style
>       net/mlx5: Remove not-needed IPsec config
>       net/mlx5: Move IPsec file to relevant directory
>       net/mlx5: Reduce kconfig complexity while building crypto support
>       net/mlx5: Remove ipsec_ops function table
>       net/mlx5: Remove not-implemented IPsec capabilities

Pulled to rdma for-next

Thanks,
Jason

  parent reply	other threads:[~2022-04-12 13:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-09  5:53 [GIT PULL] Please pull mlx5-next changes Leon Romanovsky
2022-04-12  3:50 ` patchwork-bot+netdevbpf
2022-04-12 13:57 ` Jason Gunthorpe [this message]
2023-02-15  9:56 Leon Romanovsky
2023-02-16 19:37 ` Jakub Kicinski
2023-02-19  9:05   ` Leon Romanovsky
2023-02-16 19:40 ` patchwork-bot+netdevbpf

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=20220412135715.GA204876@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=leonro@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=saeedm@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.