diff options
| author | Eric Biggers <ebiggers@google.com> | 2019-05-21 11:46:22 -0700 |
|---|---|---|
| committer | Herbert Xu <herbert@gondor.apana.org.au> | 2019-05-30 15:25:57 +0800 |
| commit | 9c5b34c2f7eb01976a5aa29ccdb786a634e3d1e0 (patch) | |
| tree | c1f64d8dc5281dfa646e4b40fb2bd218a7afd192 /Kbuild | |
| parent | 357d065a44cdd77ed5ff35155a989f2a763e96ef (diff) | |
| download | linux-stable-9c5b34c2f7eb01976a5aa29ccdb786a634e3d1e0.tar.gz linux-stable-9c5b34c2f7eb01976a5aa29ccdb786a634e3d1e0.tar.bz2 linux-stable-9c5b34c2f7eb01976a5aa29ccdb786a634e3d1e0.zip | |
crypto: jitterentropy - change back to module_init()
"jitterentropy_rng" doesn't have any other implementations, nor is it
tested by the crypto self-tests. So it was unnecessary to change it to
subsys_initcall. Also it depends on the main clocksource being
initialized, which may happen after subsys_initcall, causing this error:
jitterentropy: Initialization failed with host not compliant with requirements: 2
Change it back to module_init().
Fixes: c4741b230597 ("crypto: run initcalls for generic implementations earlier")
Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
Signed-off-by: Eric Biggers <ebiggers@google.com>
Tested-by: Geert Uytterhoeven <geert+renesas@glider.be>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'Kbuild')
0 files changed, 0 insertions, 0 deletions