Eric Biggers 231baecdef crypto: clarify name of WEAK_KEY request flag ... CRYPTO_TFM_REQ_WEAK_KEY confuses newcomers to the crypto API because it sounds like it is requesting a weak key. Actually, it is requesting that weak keys be forbidden (for algorithms that have the notion of "weak keys"; currently only DES and XTS do). Also it is only one letter away from CRYPTO_TFM_RES_WEAK_KEY, with which it can be easily confused. (This in fact happened in the UX500 driver, though just in some debugging messages.) Therefore, make the intent clear by renaming it to CRYPTO_TFM_REQ_FORBID_WEAK_KEYS. Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>		2019-01-25 18:41:52 +08:00
..
Makefile	crypto: inside-secure - add SafeXcel EIP197 crypto engine driver	2017-06-10 12:04:21 +08:00
safexcel.c	treewide: Replace more open-coded allocation size multiplications	2018-10-05 18:06:30 -07:00
safexcel.h	crypto: inside-secure - switch to SPDX identifiers	2018-07-20 13:51:22 +08:00
safexcel_cipher.c	crypto: clarify name of WEAK_KEY request flag	2019-01-25 18:41:52 +08:00
safexcel_hash.c	crypto: inside-secure - switch to SPDX identifiers	2018-07-20 13:51:22 +08:00
safexcel_ring.c	crypto: inside-secure - switch to SPDX identifiers	2018-07-20 13:51:22 +08:00