summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPaul Bolle <pebolle@tiscali.nl>2014-02-12 10:28:05 +0100
committerJiri Kosina <jkosina@suse.cz>2014-02-20 14:55:04 +0100
commit7df2482fc1d32f9fec3b0102c446bafa5646a86e (patch)
tree210d0b732be47d49e19a53c15ecb605de73922df
parentd4263348f796f29546f90802177865dd4379dd0a (diff)
downloadblackbird-op-linux-7df2482fc1d32f9fec3b0102c446bafa5646a86e.tar.gz
blackbird-op-linux-7df2482fc1d32f9fec3b0102c446bafa5646a86e.zip
doc: Insert MODULE_ in module-signing macros
Signed-off-by: Paul Bolle <pebolle@tiscali.nl> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
-rw-r--r--Documentation/module-signing.txt10
1 files changed, 5 insertions, 5 deletions
diff --git a/Documentation/module-signing.txt b/Documentation/module-signing.txt
index 2b40e04d3c49..09b583e38907 100644
--- a/Documentation/module-signing.txt
+++ b/Documentation/module-signing.txt
@@ -77,11 +77,11 @@ This has a number of options available:
This presents a choice of which hash algorithm the installation phase will
sign the modules with:
- CONFIG_SIG_SHA1 "Sign modules with SHA-1"
- CONFIG_SIG_SHA224 "Sign modules with SHA-224"
- CONFIG_SIG_SHA256 "Sign modules with SHA-256"
- CONFIG_SIG_SHA384 "Sign modules with SHA-384"
- CONFIG_SIG_SHA512 "Sign modules with SHA-512"
+ CONFIG_MODULE_SIG_SHA1 "Sign modules with SHA-1"
+ CONFIG_MODULE_SIG_SHA224 "Sign modules with SHA-224"
+ CONFIG_MODULE_SIG_SHA256 "Sign modules with SHA-256"
+ CONFIG_MODULE_SIG_SHA384 "Sign modules with SHA-384"
+ CONFIG_MODULE_SIG_SHA512 "Sign modules with SHA-512"
The algorithm selected here will also be built into the kernel (rather
than being a module) so that modules signed with that algorithm can have
OpenPOWER on IntegriCloud