From: Saeed Mahameed <saeed@kernel.org>
To: Leon Romanovsky <leon@kernel.org>
Cc: Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Leon Romanovsky <leonro@nvidia.com>,
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: Mon, 4 Apr 2022 17:35:00 -0700 [thread overview]
Message-ID: <20220405003500.duivahirienxrkuk@sx1> (raw)
In-Reply-To: <cover.1649073691.git.leonro@nvidia.com>
On 04 Apr 15:08, 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.
>
Other than the renaming ktls => tls comment, which is not a big deal
anyhow. The series looks great.
Reviewed-by: Saeed Mahameed <saeedm@nvidia.com>
next prev parent reply other threads:[~2022-04-05 1:25 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 ` Saeed Mahameed [this message]
2022-04-06 7:04 ` [PATCH mlx5-next 0/5] Drop Mellanox FPGA TLS support from the kernel Leon Romanovsky
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=20220405003500.duivahirienxrkuk@sx1 \
--to=saeed@kernel.org \
--cc=jgg@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--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