[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1704146.ryraC2p2Bb@tauon.atsec.com>
Date: Thu, 16 Jun 2016 17:40:50 +0200
From: Stephan Mueller <smueller@...onox.de>
To: Raveendra Padasalagi <raveendra.padasalagi@...adcom.com>
Cc: Herbert Xu <herbert@...dor.apana.org.au>,
"David S. Miller" <davem@...emloft.net>,
linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org,
Jon Mason <jonmason@...adcom.com>,
Florian Fainelli <f.fainelli@...il.com>,
Anup Patel <anup.patel@...adcom.com>,
Ray Jui <rjui@...adcom.com>,
Scott Branden <sbranden@...adcom.com>,
Pramod Kumar <pramod.kumar@...adcom.com>,
bcm-kernel-feedback-list <bcm-kernel-feedback-list@...adcom.com>,
Jeff Garzik <jeff@...zik.org>, Jeff Garzik <jgarzik@...hat.com>
Subject: Re: [PATCH 1/2] Crypto: Add SHA-3 hash algorithm
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
Powered by blists - more mailing lists