From: Denis Kenzior <denkenz@gmail.com>
To: ell@lists.01.org
Subject: Re: [PATCH] unit: Add runtime check for TLS suite cipher support
Date: Sun, 17 Feb 2019 20:43:10 -0600 [thread overview]
Message-ID: <364ff69a-b34f-e191-6453-4e5b4eaf0dca@gmail.com> (raw)
In-Reply-To: <20190215220137.7592-1-mathew.j.martineau@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 370 bytes --]
Hi Mat,
On 02/15/2019 04:01 PM, Mat Martineau wrote:
> Skip TLS suite tests where the currently running kernel does not have
> support for the necessary cipher. Checksums types already have runtime
> validation.
> ---
> unit/test-tls.c | 21 ++++++++++++++++++---
> 1 file changed, 18 insertions(+), 3 deletions(-)
Applied, thanks.
Regards,
-Denis
prev parent reply other threads:[~2019-02-18 2:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 22:01 [PATCH] unit: Add runtime check for TLS suite cipher support Mat Martineau
2019-02-18 2:43 ` Denis Kenzior [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=364ff69a-b34f-e191-6453-4e5b4eaf0dca@gmail.com \
--to=denkenz@gmail.com \
--cc=ell@lists.01.org \
/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.