Merge branch 'i2c/for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/wsa...

[deliverable/linux.git] / Documentation / module-signing.txt

diff --git a/Documentation/module-signing.txt b/Documentation/module-signing.txt
index 2429024c0749d7f6df02ee97100c0e77ba759174..09c2382ad0556b196a3b4bb941b9e86597e8ebc5 100644 (file)
--- a/Documentation/module-signing.txt
+++ b/Documentation/module-signing.txt
@@ -78,11 +78,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