From: Marcus Meissner <meissner@suse.de>
To: Stephan Mueller <smueller@chronox.de>
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] crypto: testmgr: mark more algorithms as FIPS compliant
Date: Fri, 5 Feb 2016 14:42:41 +0100 [thread overview]
Message-ID: <20160205134241.GC14228@suse.de> (raw)
In-Reply-To: <2304471.iOLiAjeuEP@tauon.atsec.com>
On Fri, Feb 05, 2016 at 02:41:01PM +0100, Stephan Mueller wrote:
> Am Freitag, 5. Februar 2016, 14:22:25 schrieb Marcus Meissner:
>
> Hi Marcus,
>
> >Some more authenc() wrapped algorithms are FIPS compliant, tag
> >them as such.
>
> Is this patch a duplication of the first one?
yes, I mistakenly sent it as part of a series, while it is not.
Ciao, Marcus
prev parent reply other threads:[~2016-02-05 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 13:22 [PATCH 2/2] crypto: testmgr: mark more algorithms as FIPS compliant Marcus Meissner
2016-02-05 13:41 ` Stephan Mueller
2016-02-05 13:42 ` Marcus Meissner [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=20160205134241.GC14228@suse.de \
--to=meissner@suse.de \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smueller@chronox.de \
/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).