The patch titled
add function documentation for register_chrdev()
has been removed from the -mm tree. Its filename is
add-function-documentation-for-register_chrdev.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: add function documentation for register_chrdev()
From: Rolf Eike Beer <eike-kernel@xxxxxxxxx>
Documentation for register_chrdev() was missing completely.
[akpm@xxxxxxxx: kerneldocification]
Signed-off-by: Rolf Eike Beer <eike-kernel@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
fs/char_dev.c | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff -puN fs/char_dev.c~add-function-documentation-for-register_chrdev fs/char_dev.c
--- a/fs/char_dev.c~add-function-documentation-for-register_chrdev
+++ a/fs/char_dev.c
@@ -182,6 +182,28 @@ int alloc_chrdev_region(dev_t *dev, unsi
return 0;
}
+/**
+ * register_chrdev() - Register a major number for character devices.
+ * @major: major device number or 0 for dynamic allocation
+ * @name: name of this range of devices
+ * @fops: file operations associated with this devices
+ *
+ * If @major == 0 this functions will dynamically allocate a major and return
+ * its number.
+ *
+ * If @major > 0 this function will attempt to reserve a device with the given
+ * major number and will return zero on success.
+ *
+ * Returns a -ve errno on failure.
+ *
+ * The name of this device has nothing to do with the name of the device in
+ * /dev. It only helps to keep track of the different owners of devices. If
+ * your module name has only one type of devices it's ok to use e.g. the name
+ * of the module here.
+ *
+ * This function registers a range of 256 minor numbers. The first minor number
+ * is 0.
+ */
int register_chrdev(unsigned int major, const char *name,
const struct file_operations *fops)
{
_
Patches currently in -mm which might be from eike-kernel@xxxxxxxxx are
git-mtd.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
