lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 2 Mar 2022 12:24:21 +1200 From: Herbert Xu <herbert@...dor.apana.org.au> To: "Jason A. Donenfeld" <Jason@...c4.com> Cc: Tianjia Zhang <tianjia.zhang@...ux.alibaba.com>, "David S. Miller" <davem@...emloft.net>, Catalin Marinas <catalin.marinas@....com>, Will Deacon <will@...nel.org>, Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>, "H. Peter Anvin" <hpa@...or.com>, Gilad Ben-Yossef <gilad@...yossef.com>, Ard Biesheuvel <ard.biesheuvel@...aro.org>, "Markku-Juhani O . Saarinen" <mjos@....fi>, Jussi Kivilinna <jussi.kivilinna@....fi>, x86@...nel.org, linux-crypto@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 1/3] crypto: sm4 - create SM4 library based on sm4 generic code On Tue, Mar 01, 2022 at 11:34:28AM +0100, Jason A. Donenfeld wrote: > > lib/crypto/Kconfig | 3 + > > lib/crypto/Makefile | 3 + > > lib/crypto/sm4.c | 184 +++++++++++++++++++++++++++++++++++++++++++ > > If this is only used by the crypto API, it does not belong in > lib/crypto. Nope there is no such rule. lib/crypto is fine if you're adding code that is shared between crypto and arch/*/crypto. Cheers, -- Email: Herbert Xu <herbert@...dor.apana.org.au> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Powered by blists - more mailing lists