From: Stephan Mueller Subject: Re: [PATCH 1/2] Crypto: Add SHA-3 hash algorithm Date: Thu, 16 Jun 2016 17:40:50 +0200 Message-ID: <1704146.ryraC2p2Bb@tauon.atsec.com> References: <1465983719-8313-1-git-send-email-raveendra.padasalagi@broadcom.com> <8163378.RZGaC46RvE@tauon.atsec.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: Herbert Xu , "David S. Miller" , linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org, Jon Mason , Florian Fainelli , Anup Patel , Ray Jui , Scott Branden , Pramod Kumar , bcm-kernel-feedback-list , Jeff Garzik , Jeff Garzik To: Raveendra Padasalagi Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-crypto.vger.kernel.org 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