From: Kleber Sacilotto de Souza <klebers@linux.vnet.ibm.com>
To: linux-scsi@vger.kernel.org
Cc: Kleber Sacilotto de Souza <klebers@linux.vnet.ibm.com>
Subject: [PATCH] Documentation: fix documentation of scsi_add_device()
Date: Wed, 7 Jul 2010 10:35:49 -0300 [thread overview]
Message-ID: <1278509749-449-1-git-send-email-klebers@linux.vnet.ibm.com> (raw)
This patch fixes the documentation of the parameters and return value of
scsi_add_device().
Signed-off-by: Kleber Sacilotto de Souza <klebers@linux.vnet.ibm.com>
---
Documentation/scsi/scsi_mid_low_api.txt | 11 ++++-------
1 files changed, 4 insertions(+), 7 deletions(-)
diff --git a/Documentation/scsi/scsi_mid_low_api.txt b/Documentation/scsi/scsi_mid_low_api.txt
index de67229..e53fbf2 100644
--- a/Documentation/scsi/scsi_mid_low_api.txt
+++ b/Documentation/scsi/scsi_mid_low_api.txt
@@ -416,12 +416,10 @@ void scsi_activate_tcq(struct scsi_device *sdev, int depth)
* scsi_add_device - creates new scsi device (lu) instance
* @shost: pointer to scsi host instance
* @channel: channel number (rarely other than 0)
- * @id: target id number
+ * @target: target number
* @lun: logical unit number
*
- * Returns pointer to new struct scsi_device instance or
- * ERR_PTR(-ENODEV) (or some other bent pointer) if something is
- * wrong (e.g. no lu responds at given address)
+ * Returns 0 on success, negative errno on failure (e.g. -ENODEV)
*
* Might block: yes
*
@@ -434,9 +432,8 @@ void scsi_activate_tcq(struct scsi_device *sdev, int depth)
*
* Defined in: drivers/scsi/scsi_scan.c
**/
-struct scsi_device * scsi_add_device(struct Scsi_Host *shost,
- unsigned int channel,
- unsigned int id, unsigned int lun)
+int scsi_add_device(struct Scsi_Host *host, uint channel,
+ uint target, uint lun)
/**
--
1.7.0.4
reply other threads:[~2010-07-07 13:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1278509749-449-1-git-send-email-klebers@linux.vnet.ibm.com \
--to=klebers@linux.vnet.ibm.com \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).