From: Stephan Mueller <smueller@chronox.de>
To: Raveendra Padasalagi <raveendra.padasalagi@broadcom.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
Jon Mason <jonmason@broadcom.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Anup Patel <anup.patel@broadcom.com>, Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Pramod Kumar <pramod.kumar@broadcom.com>,
bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>,
Jeff Garzik <jeff@garzik.org>, Jeff Garzik <jgarzik@redhat.com>
Subject: Re: [PATCH 1/2] Crypto: Add SHA-3 hash algorithm
Date: Thu, 16 Jun 2016 17:40:50 +0200 [thread overview]
Message-ID: <1704146.ryraC2p2Bb@tauon.atsec.com> (raw)
In-Reply-To: <CAAFb_vq0dGbQP6gY-t0hDCqa1pBQZGeQy00RFoUww0_Gvw=kUg@mail.gmail.com>
Am Donnerstag, 16. Juni 2016, 14:44:57 schrieb Raveendra Padasalagi:
Hi Raveendra,
> > Typo DFIPS?
>
> It's not typo, DFIPS mean here Draft FIPS 202.
> Do you want me to put it in another way ?
I have never seen DFIPS. Besides, most FIPS standards are drafts (including of
FIPS 140-2 :-) ), because it would require a signature from some ministry big-
wig in the US govt to "release" it. Hence, I expect that it would retain its
draft state for a long time :-)
But if DFIPS is what you think is right, leave it :-)
Ciao
Stephan
next prev parent reply other threads:[~2016-06-16 15:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 9:41 [PATCH 0/2] Add SHA-3 algorithm and test vectors Raveendra Padasalagi
2016-06-15 9:41 ` [PATCH 1/2] Crypto: Add SHA-3 hash algorithm Raveendra Padasalagi
2016-06-15 11:42 ` Stephan Mueller
2016-06-16 9:14 ` Raveendra Padasalagi
2016-06-16 15:40 ` Stephan Mueller [this message]
2016-06-16 16:09 ` Raveendra Padasalagi
2016-06-16 16:24 ` Stephan Mueller
2016-06-15 9:41 ` [PATCH 2/2] Crypto: Add SHA-3 Test's in tcrypt Raveendra Padasalagi
2016-06-15 9:50 ` Raveendra Padasalagi
2016-06-15 9:50 ` [PATCH 0/2] Add SHA-3 algorithm and test vectors Raveendra Padasalagi
2016-06-15 10:57 ` Raveendra Padasalagi
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=1704146.ryraC2p2Bb@tauon.atsec.com \
--to=smueller@chronox.de \
--cc=anup.patel@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=jeff@garzik.org \
--cc=jgarzik@redhat.com \
--cc=jonmason@broadcom.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pramod.kumar@broadcom.com \
--cc=raveendra.padasalagi@broadcom.com \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.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