UPSTREAM: crypto: jitter - fix comments

One should not say "ec can be NULL" and then dereference it.
One cannot talk about the return value if the function returns void.

Signed-off-by: Alexander E. Patrakov <patrakov@gmail.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>

Bug: 153614920
(cherry picked from commit e1f653cbe7dd615edc8e3ffe396be03068feed81)
Change-Id: I6d632ae5482117dbea836f6eb06c6f50329d19bc
Signed-off-by: Eric Biggers <ebiggers@google.com>
This commit is contained in:
Alexander E. Patrakov 2019-09-18 12:28:49 +05:00 • committed by Alexander Martinz
commit 4734d106f5
No known key found for this signature in database
GPG key ID: CF15BDD9A321A9B2

View file

@ -172,7 +172,7 @@ static __u64 jent_loop_shuffle(struct rand_data *ec,
* implies that careful retesting must be done.
*
* Input:
* @ec entropy collector struct -- may be NULL
* @ec entropy collector struct
* @time time stamp to be injected
* @loop_cnt if a value not equal to 0 is set, use the given value as number of
* loops to perform the folding
@ -400,8 +400,8 @@ static void jent_gen_entropy(struct rand_data *ec)
* primes the test if needed.
*
* Return:
* 0 if FIPS test passed
* < 0 if FIPS test failed
* returns normally if FIPS test passed
* panics the kernel if FIPS test failed
*/
static void jent_fips_test(struct rand_data *ec)
{