- dont-assume-arguments-to-init-have-no-period-in-them.patch removed from -mm tree

- dont-assume-arguments-to-init-have-no-period-in-them.patch removed from -mm tree

[akpm]

The patch titled
     Don't assume arguments to init have no period in them.
has been removed from the -mm tree.  Its filename was
     dont-assume-arguments-to-init-have-no-period-in-them.patch

This patch was dropped because an updated version will be merged

------------------------------------------------------
Subject: Don't assume arguments to init have no period in them.
From: Rob Landley <rob@landley.net>

The kernel assumes that nobody will ever legitimately feed in a kernel
command line option with a period in it, and the kernel is wrong: I'm
feeding the path to a script as an argument to my init program, the name of
the script ends in .sh.

I've been using this patch ever since 2.6.13, and I still need it.

Signed-off-by: Rob Landley <rob@landley.net>
Cc: Rusty Russell <rusty@rustcorp.com.au>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 init/main.c |    9 ---------
 1 file changed, 9 deletions(-)

diff -puN init/main.c~dont-assume-arguments-to-init-have-no-period-in-them init/main.c
--- a/init/main.c~dont-assume-arguments-to-init-have-no-period-in-them
+++ a/init/main.c
@@ -273,15 +273,6 @@ static int __init unknown_bootoption(cha
 	if (obsolete_checksetup(param))
 		return 0;
 
-	/*
-	 * Preemptive maintenance for "why didn't my mispelled command
-	 * line work?"
-	 */
-	if (strchr(param, '.') && (!val || strchr(param, '.') < val)) {
-		printk(KERN_ERR "Unknown boot option `%s': ignoring\n", param);
-		return 0;
-	}
-
 	if (panic_later)
 		return 0;
 
_

Patches currently in -mm which might be from rob@landley.net are

dont-assume-arguments-to-init-have-no-period-in-them.patch