[PATCH -rc7] 3rd try: Documentation/ABI: devfs is not obsolete, butremoved!

From: jens m. noedler
Date: Sat Sep 16 2006 - 13:01:06 EST


Hi everybody, Greg, Linus,

This little patch just moves the devfs entry from ABI/obsolete to
ABI/removed, and adds the comment, that devfs was removed in 2.6.18.

The patch was send on 3. Sep and 9. Sep 2006 to the LKML but nobody
picked it up, so here is another chance. :-)

The patch is against linus' current git tree and it would be nice to
see it in the final 2.6.18 kernel.

Please cc: me! Kind regards, Jens


Signed-off-by: jens m. noedler <noedler@xxxxxx>

---

diff --git a/Documentation/ABI/obsolete/devfs b/Documentation/ABI/obsolete/devfs
deleted file mode 100644
index b8b8739..0000000
--- a/Documentation/ABI/obsolete/devfs
+++ /dev/null
@@ -1,13 +0,0 @@
-What: devfs
-Date: July 2005
-Contact: Greg Kroah-Hartman <gregkh@xxxxxxx>
-Description:
- devfs has been unmaintained for a number of years, has unfixable
- races, contains a naming policy within the kernel that is
- against the LSB, and can be replaced by using udev.
- The files fs/devfs/*, include/linux/devfs_fs*.h will be removed,
- along with the the assorted devfs function calls throughout the
- kernel tree.
-
-Users:
-
diff --git a/Documentation/ABI/removed/devfs b/Documentation/ABI/removed/devfs
new file mode 100644
index 0000000..8195c4e
--- /dev/null
+++ b/Documentation/ABI/removed/devfs
@@ -0,0 +1,12 @@
+What: devfs
+Date: July 2005 (scheduled), finally removed in kernel v2.6.18
+Contact: Greg Kroah-Hartman <gregkh@xxxxxxx>
+Description:
+ devfs has been unmaintained for a number of years, has unfixable
+ races, contains a naming policy within the kernel that is
+ against the LSB, and can be replaced by using udev.
+ The files fs/devfs/*, include/linux/devfs_fs*.h were removed,
+ along with the the assorted devfs function calls throughout the
+ kernel tree.
+
+Users:


--
jens m. noedler
noedler@xxxxxx
pgp: 0x9f0920bb
http://noedler.de
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/