Skip to content

No longer default to HW_RANDOM when UML_RANDOM is the trigger

Dragan Simic linux-crypto lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest3 patches 7 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/3hwrng: Use tabs as leading whitespace consistently in Kconfigdrivers/char/hw_random/Kconfig+4 -40 replies
2/3hwrng: Move one "tristate" Kconfig description to the usual placedrivers/char/hw_random/Kconfig+1 -10 replies
3/3hwrng: Don't default to HW_RANDOM when UML_RANDOM is the triggerdrivers/char/hw_random/Kconfig+38 -386 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/3] No longer default to HW_RANDOM when UML_RANDOM is the trigger

This is a small patch series that makes the already existing HW_RANDOM_* options in the hw_random Kconfig selected by default only when the UML_RANDOM option isn't already selected. Having the HW_RANDOM_* options selected doesn't make much sense for user-mode Linux (UML), which obviously cannot make use of any HWRNG devices.

Along the way, some additional trivial cleanups of the hw_random Kconfig file are also performed as spotted, in separate patches.

Dragan Simic (3):
hwrng: Use tabs as leading whitespace consistently in Kconfig
hwrng: Move one "tristate" Kconfig description to the usual place
hwrng: Don't default to HW_RANDOM when UML_RANDOM is the trigger

 drivers/char/hw_random/Kconfig | 84 +++++++++++++++++-----------------
 1 file changed, 42 insertions(+), 42 deletions(-)