linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leon Romanovsky <leonro@nvidia.com>
To: Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Jason Gunthorpe <jgg@nvidia.com>, <linux-kernel@vger.kernel.org>,
	<linux-rdma@vger.kernel.org>, <netdev@vger.kernel.org>,
	Saeed Mahameed <saeedm@nvidia.com>,
	Tariq Toukan <tariqt@nvidia.com>
Subject: Re: [PATCH mlx5-next 0/5] Drop Mellanox FPGA TLS support from the kernel
Date: Wed, 6 Apr 2022 10:04:14 +0300	[thread overview]
Message-ID: <Yk07bqnHhuT8QjS7@unreal> (raw)
In-Reply-To: <cover.1649073691.git.leonro@nvidia.com>

On Mon, Apr 04, 2022 at 03:08:14PM +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <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
>     
> Thanks
> 
> BTW, the target of this series is mlx5-next, as other series removes
> FPGA IPsec together with relevant cleanup in RDMA side.
> 
> Leon Romanovsky (5):
>   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
> 

Thanks, applied to mlx5-next.

7a9104ea9011 net/mlx5: Cleanup kTLS function names and their exposure
943aa7bda373 net/mlx5: Remove tls vs. ktls separation as it is the same
691f17b980d0 net/mlx5: Remove indirection in TLS build
e59437aa7ae6 net/mlx5: Reliably return TLS device capabilities
40379a0084c2 net/mlx5_fpga: Drop INNOVA TLS support

      parent reply	other threads:[~2022-04-06 10:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04 12:08 [PATCH mlx5-next 0/5] Drop Mellanox FPGA TLS support from the kernel Leon Romanovsky
2022-04-04 12:08 ` [PATCH mlx5-next 1/5] net/mlx5_fpga: Drop INNOVA TLS support Leon Romanovsky
2022-04-04 12:08 ` [PATCH mlx5-next 2/5] net/mlx5: Reliably return TLS device capabilities Leon Romanovsky
2022-04-04 12:08 ` [PATCH mlx5-next 3/5] net/mlx5: Remove indirection in TLS build Leon Romanovsky
2022-04-04 12:08 ` [PATCH mlx5-next 4/5] net/mlx5: Remove tls vs. ktls separation as it is the same Leon Romanovsky
2022-04-05  0:33   ` Saeed Mahameed
2022-04-05  5:43     ` Leon Romanovsky
2022-04-05 17:20       ` Saeed Mahameed
2022-04-05 18:32         ` Leon Romanovsky
2022-04-04 12:08 ` [PATCH mlx5-next 5/5] net/mlx5: Cleanup kTLS function names and their exposure Leon Romanovsky
2022-04-05  0:35 ` [PATCH mlx5-next 0/5] Drop Mellanox FPGA TLS support from the kernel Saeed Mahameed
2022-04-06  7:04 ` Leon Romanovsky [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=Yk07bqnHhuT8QjS7@unreal \
    --to=leonro@nvidia.com \
    --cc=jgg@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --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).