[PATCH][Doc] Fix parameter names in drivers/base/class.c
From: Rolf Eike Beer
Date: Fri Jul 21 2006 - 05:04:53 EST
Change parameter names to match arguments of functions.
Signed-off-by: Rolf Eike Beer <eike-kernel@xxxxxxxxx>
author Rolf Eike Beer <eike-kernel@xxxxxxxxx> Fri, 21 Jul 2006 11:02:51 +0200
committer Rolf Eike Beer <beer@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> Fri, 21 Jul 2006 11:02:51 +0200
drivers/base/class.c | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/base/class.c b/drivers/base/class.c
index de89083..89f824e 100644
@@ -226,7 +226,7 @@ error:
* class_destroy - destroys a struct class structure
- * @cs: pointer to the struct class that is to be destroyed
+ * @cls: pointer to the struct class that is to be destroyed
* Note, the pointer to be destroyed must have been created with a call
* to class_create().
@@ -656,9 +656,9 @@ int class_device_register(struct class_d
* class_device_create - creates a class device and registers it with sysfs
- * @cs: pointer to the struct class that this device should be registered to.
+ * @cls: pointer to the struct class that this device should be registered to.
* @parent: pointer to the parent struct class_device of this new device, if any.
- * @dev: the dev_t for the char device to be added.
+ * @devt: the dev_t for the char device to be added.
* @device: a pointer to a struct device that is assiociated with this class device.
* @fmt: string for the class device's name
@@ -763,7 +763,7 @@ void class_device_unregister(struct clas
* class_device_destroy - removes a class device that was created with class_device_create()
* @cls: the pointer to the struct class that this device was registered * with.
- * @dev: the dev_t of the device that was previously registered.
+ * @devt: the dev_t of the device that was previously registered.
* This call unregisters and cleans up a class device that was created with a
* call to class_device_create()
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/