From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Olivier Sobrie <olivier.sobrie@silexinsight.com>,
Waleed Ziad <waleed94ziad@gmail.com>,
Matt Mackall <mpm@selenic.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH] hwrng: ba431 - HW_RANDOM_BA431 should not default to y
Date: Tue, 30 Jun 2020 15:39:41 +0200 [thread overview]
Message-ID: <20200630133941.28696-1-geert+renesas@glider.be> (raw)
As HW_RANDOM_BA431 does not have any platform dependency, it should not
default to enabled.
Fixes: 0289e9be5dc26d84 ("hwrng: ba431 - add support for BA431 hwrng")
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
drivers/char/hw_random/Kconfig | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/char/hw_random/Kconfig b/drivers/char/hw_random/Kconfig
index 7b876dfdbaafe7ad..9e91c556942b1c94 100644
--- a/drivers/char/hw_random/Kconfig
+++ b/drivers/char/hw_random/Kconfig
@@ -76,7 +76,6 @@ config HW_RANDOM_ATMEL
config HW_RANDOM_BA431
tristate "Silex Insight BA431 Random Number Generator support"
- default HW_RANDOM
help
This driver provides kernel-side support for the Random Number
Generator hardware based on Silex Insight BA431 IP.
@@ -84,8 +83,6 @@ config HW_RANDOM_BA431
To compile this driver as a module, choose M here: the
module will be called ba431-rng.
- If unsure, say Y.
-
config HW_RANDOM_BCM2835
tristate "Broadcom BCM2835/BCM63xx Random Number Generator support"
depends on ARCH_BCM2835 || ARCH_BCM_NSP || ARCH_BCM_5301X || \
--
2.17.1
next reply other threads:[~2020-06-30 13:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 13:39 Geert Uytterhoeven [this message]
2020-07-09 12:54 ` [PATCH] hwrng: ba431 - HW_RANDOM_BA431 should not default to y 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=20200630133941.28696-1-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=olivier.sobrie@silexinsight.com \
--cc=waleed94ziad@gmail.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;
as well as URLs for NNTP newsgroup(s).