From: Dragan Simic <dsimic@manjaro.org>
To: linux-crypto@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, olivia@selenic.com,
herbert@gondor.apana.org.au, didi.debian@cknow.org,
heiko@sntech.de, dsimic@manjaro.org
Subject: [PATCH 0/3] No longer default to HW_RANDOM when UML_RANDOM is the trigger
Date: Wed, 15 Jan 2025 14:06:59 +0100 [thread overview]
Message-ID: <cover.1736946020.git.dsimic@manjaro.org> (raw)
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(-)
next reply other threads:[~2025-01-15 13:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 13:06 Dragan Simic [this message]
2025-01-15 13:07 ` [PATCH 1/3] hwrng: Use tabs as leading whitespace consistently in Kconfig Dragan Simic
2025-01-15 13:07 ` [PATCH 2/3] hwrng: Move one "tristate" Kconfig description to the usual place Dragan Simic
2025-01-15 13:07 ` [PATCH 3/3] hwrng: Don't default to HW_RANDOM when UML_RANDOM is the trigger Dragan Simic
2025-01-15 14:59 ` Diederik de Haas
2025-01-15 17:21 ` Dragan Simic
2025-02-09 9:15 ` Herbert Xu
2025-02-09 9:37 ` Dragan Simic
2025-02-09 9:54 ` Herbert Xu
2025-02-09 10:13 ` Dragan Simic
2025-02-09 10:22 ` [PATCH 0/3] No longer " Herbert Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1736946020.git.dsimic@manjaro.org \
--to=dsimic@manjaro.org \
--cc=didi.debian@cknow.org \
--cc=heiko@sntech.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olivia@selenic.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox