[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180830194505.4778-1-thibaut@sautereau.fr>
Date: Thu, 30 Aug 2018 21:45:05 +0200
From: Thibaut Sautereau <thibaut@...tereau.fr>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Ingo Molnar <mingo@...nel.org>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Randy Dunlap <rdunlap@...radead.org>,
Arnd Bergmann <arnd@...db.de>,
Masami Hiramatsu <mhiramat@...nel.org>,
Waiman Long <longman@...hat.com>,
Mikulas Patocka <mpatocka@...hat.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
linux-kernel@...r.kernel.org
Subject: [PATCH] lib: fix three typos in Kconfig help text
Fix three typos in CONFIG_WARN_ALL_UNSEEDED_RANDOM help text.
Signed-off-by: Thibaut Sautereau <thibaut@...tereau.fr>
---
lib/Kconfig.debug | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index c7fef0c56d6b..3e50cc93572c 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -1277,13 +1277,13 @@ config WARN_ALL_UNSEEDED_RANDOM
time. This is really bad from a security perspective, and
so architecture maintainers really need to do what they can
to get the CRNG seeded sooner after the system is booted.
- However, since users can not do anything actionble to
+ However, since users cannot do anything actionable to
address this, by default the kernel will issue only a single
warning for the first use of unseeded randomness.
Say Y here if you want to receive warnings for all uses of
unseeded randomness. This will be of use primarily for
- those developers interersted in improving the security of
+ those developers interested in improving the security of
Linux kernels running on their architecture (or
subarchitecture).
--
2.18.0
Powered by blists - more mailing lists