mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: lkml <linux-kernel@vger.kernel.org>
Cc: gregkh <greg@kroah.com>
Subject: [PATCH] kernel-doc: drivers/base fixes
Date: Sun, 23 Oct 2005 11:59:14 -0700	[thread overview]
Message-ID: <20051023115914.51f96ddc.rdunlap@xenotime.net> (raw)

From: Randy Dunlap <rdunlap@xenotime.net>

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

Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
---

 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


---

             reply	other threads:[~2005-10-23 19:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-23 18:59 Randy.Dunlap [this message]
2005-10-28  6:30 [PATCH] drivers/base - fix sparse warnings Greg KH
2005-10-28  6:30 ` [PATCH] kernel-doc: drivers/base fixes Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20051023115914.51f96ddc.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®