[PATCH] kernel-doc: drivers/base fixes

[Randy.Dunlap]

From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>

driver/base: add missing function parameters; eliminate all warnings.

Signed-off-by: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
---

 drivers/base/core.c   |    4 ++--
 drivers/base/driver.c |    3 ++-
 2 files changed, 4 insertions(+), 3 deletions(-)

diff -Naurp linux-2614-rc5/drivers/base/driver.c~kdoc_base linux-2614-rc5/drivers/base/driver.c
--- linux-2614-rc5/drivers/base/driver.c~kdoc_base	2005-10-20 18:55:31.000000000 -0700
+++ linux-2614-rc5/drivers/base/driver.c	2005-10-22 22:27:37.000000000 -0700
@@ -28,6 +28,7 @@ static struct device * next_device(struc
 /**
  *	driver_for_each_device - Iterator for devices bound to a driver.
  *	@drv:	Driver we're iterating.
+ *	@start: Device to begin with
  *	@data:	Data to pass to the callback.
  *	@fn:	Function to call for each device.
  *
@@ -57,7 +58,7 @@ EXPORT_SYMBOL_GPL(driver_for_each_device
 
 /**
  * driver_find_device - device iterator for locating a particular device.
- * @driver: The device's driver
+ * @drv: The device's driver
  * @start: Device to begin with
  * @data: Data to pass to match function
  * @match: Callback function to check device
diff -Naurp linux-2614-rc5/drivers/base/core.c~kdoc_base linux-2614-rc5/drivers/base/core.c
--- linux-2614-rc5/drivers/base/core.c~kdoc_base	2005-10-20 18:55:31.000000000 -0700
+++ linux-2614-rc5/drivers/base/core.c	2005-10-22 22:24:58.000000000 -0700
@@ -390,11 +390,11 @@ static struct device * next_device(struc
 
 /**
  *	device_for_each_child - device child iterator.
- *	@dev:	parent struct device.
+ *	@parent: parent struct device.
  *	@data:	data for the callback.
  *	@fn:	function to be called for each device.
  *
- *	Iterate over @dev's child devices, and call @fn for each,
+ *	Iterate over @parent's child devices, and call @fn for each,
  *	passing it @data.
  *
  *	We check the return of @fn each time. If it returns anything


---
-
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/