On Tue, May 21, 2019 at 8:46 PM Eric Biggers <[email protected]> wrote: > From: Eric Biggers <[email protected]> > > "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 <[email protected]> > Signed-off-by: Eric Biggers <[email protected]>
Tested-by: Geert Uytterhoeven <[email protected]> Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected] In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
