param: don't complain about unused module parameters.

Jon confirms that recent modprobe will look in /proc/cmdline, so these
cmdline options can still be used.

See http://bugzilla.kernel.org/show_bug.cgi?id=14164

Reported-by: Adam Williamson <awilliam@redhat.com>
Cc: stable@kernel.org
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

1 files changed, 3 insertions, 8 deletions

diff --git a/init/main.c b/init/main.c
index 5988debfc505..4051d75dd2d6 100644
--- a/init/main.c
+++ b/init/main.c
@@ -251,7 +251,7 @@ early_param("loglevel", loglevel);
 
 /*
  * Unknown boot options get handed to init, unless they look like
- * failed parameters
+ * unused parameters (modprobe will find them in /proc/cmdline).
  */
 static int __init unknown_bootoption(char *param, char *val)
 {
@@ -272,14 +272,9 @@ static int __init unknown_bootoption(char *param, char *val)
         if (obsolete_checksetup(param))
                 return 0;
 
-        /*
-         * Preemptive maintenance for "why didn't my misspelled command
-         * line work?"
-         */
-        if (strchr(param, '.') && (!val || strchr(param, '.') < val)) {
-                printk(KERN_ERR "Unknown boot option `%s': ignoring\n", param);
+        /* Unused module parameter. */
+        if (strchr(param, '.') && (!val || strchr(param, '.') < val))
                 return 0;
-        }
 
         if (panic_later)
                 return 0;