From: Jakub Kicinski <kuba@kernel.org>
To: Rishikesh Jethwani <rjethwani@purestorage.com>
Cc: netdev@vger.kernel.org, saeedm@nvidia.com, tariqt@nvidia.com,
mbloch@nvidia.com, borisp@nvidia.com, john.fastabend@gmail.com,
sd@queasysnail.net, davem@davemloft.net, pabeni@redhat.com,
edumazet@google.com, leon@kernel.org
Subject: Re: [PATCH v5 0/3] tls: Add TLS 1.3 hardware offload support
Date: Tue, 3 Feb 2026 14:42:33 -0800 [thread overview]
Message-ID: <20260203144233.053321b4@kernel.org> (raw)
In-Reply-To: <CAKaoeS29J7bONONKF8mjyuW3zkW1=hrNx6oFCyPOvv+s=i5pAA@mail.gmail.com>
On Tue, 3 Feb 2026 10:55:33 -0800 Rishikesh Jethwani wrote:
> On Mon, Jan 26, 2026 at 4:16 PM Jakub Kicinski <kuba@kernel.org> wrote:
> > > I ran the TLS selftests - all 898 tests pass:
> > > linux-kselftest/tools/testing/selftests/net# ./tls 2>&1 | tee tls_test.log
> > > # PASSED: 898 / 898 tests passed.
> > > # Totals: pass:898 fail:0 xfail:0 xpass:0 skip:0 error:0
> >
> > I am asking you to implement selftests that will test the HW.
>
> v6 introduces a selftest to verify hardware offload functionality
> https://lore.kernel.org/netdev/20260203184835.3619101-1-rjethwani@purestorage.com/
no need to ping people that a new version has been posted if you're
already CCing them on said new version
prev parent reply other threads:[~2026-02-03 22:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 19:28 [PATCH v5 0/3] tls: Add TLS 1.3 hardware offload support Rishikesh Jethwani
2026-01-22 19:28 ` [PATCH v5 1/3] tls: add " Rishikesh Jethwani
2026-01-22 19:28 ` [PATCH v5 2/3] tls: add hardware offload key update support Rishikesh Jethwani
2026-01-22 19:28 ` [PATCH v5 3/3] mlx5: TLS 1.3 hardware offload support Rishikesh Jethwani
2026-01-23 1:48 ` [PATCH v5 0/3] tls: Add " Jakub Kicinski
2026-01-23 19:03 ` Rishikesh Jethwani
2026-01-26 22:07 ` Rishikesh Jethwani
2026-01-27 0:16 ` Jakub Kicinski
2026-02-03 18:55 ` Rishikesh Jethwani
2026-02-03 22:42 ` Jakub Kicinski [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=20260203144233.053321b4@kernel.org \
--to=kuba@kernel.org \
--cc=borisp@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=john.fastabend@gmail.com \
--cc=leon@kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rjethwani@purestorage.com \
--cc=saeedm@nvidia.com \
--cc=sd@queasysnail.net \
--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.