linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephan Mueller <smueller@chronox.de>
To: Tadeusz Struk <tadeusz.struk@intel.com>
Cc: herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org
Subject: Re: [PATCH] crypto: testmgr - don't print info about missing test for gcm-aes-aesni
Date: Wed, 24 Jun 2015 16:44:13 +0200	[thread overview]
Message-ID: <1441660.1IFzzoL80j@tauon.atsec.com> (raw)
In-Reply-To: <20150624141422.30488.59869.stgit@tstruk-mobl1>

Am Mittwoch, 24. Juni 2015, 07:14:22 schrieb Tadeusz Struk:

Hi Tadeusz,

>Don't print info about missing test for the internal
>helper __driver-gcm-aes-aesni
>
>Signed-off-by: Tadeusz Struk <tadeusz.struk@intel.com>
>---
> crypto/testmgr.c |    3 +++
> 1 file changed, 3 insertions(+)
>
>diff --git a/crypto/testmgr.c b/crypto/testmgr.c
>index 975e1ea..ad4c3e3 100644
>--- a/crypto/testmgr.c
>+++ b/crypto/testmgr.c
>@@ -2056,6 +2056,9 @@ static const struct alg_test_desc alg_test_descs[] = {
> 		.alg = "__driver-ecb-twofish-avx",
> 		.test = alg_test_null,
> 	}, {
>+		.alg = "__driver-gcm-aes-aesni",
>+		.test = alg_test_null,

Wouldn't fips_allowed = 1 be needed here?
>+	}, {
> 		.alg = "__ghash-pclmulqdqni",
> 		.test = alg_test_null,
> 		.fips_allowed = 1,
>
>--
>To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html


Ciao
Stephan

  reply	other threads:[~2015-06-24 14:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-24 14:14 [PATCH] crypto: testmgr - don't print info about missing test for gcm-aes-aesni Tadeusz Struk
2015-06-24 14:44 ` Stephan Mueller [this message]
2015-06-24 15:47   ` Tadeusz Struk

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=1441660.1IFzzoL80j@tauon.atsec.com \
    --to=smueller@chronox.de \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=tadeusz.struk@intel.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).