From: Christoph Hellwig <hch@lst.de>
To: James.Bottomley@steeleye.com
Cc: linux-scsi@vger.kernel.org
Subject: [PATCH] kill reamining scsi_scan.c typedef abuse
Date: Tue, 3 Jun 2003 23:05:38 +0200 [thread overview]
Message-ID: <20030603210538.GC9336@lst.de> (raw)
diff -Nru a/drivers/scsi/scsi_scan.c b/drivers/scsi/scsi_scan.c
--- a/drivers/scsi/scsi_scan.c Sun Jun 1 21:27:34 2003
+++ b/drivers/scsi/scsi_scan.c Sun Jun 1 21:27:34 2003
@@ -141,7 +141,8 @@
* @sreq to unlock a device, storing the (unused) results into result.
* Called for BLIST_KEY devices.
**/
-static void scsi_unlock_floptical(Scsi_Request *sreq, unsigned char *result)
+static void scsi_unlock_floptical(struct scsi_request *sreq,
+ unsigned char *result)
{
unsigned char scsi_cmd[MAX_COMMAND_SIZE];
@@ -154,8 +155,7 @@
scsi_cmd[5] = 0;
sreq->sr_cmd_len = 0;
sreq->sr_data_direction = SCSI_DATA_READ;
- scsi_wait_req(sreq, (void *) scsi_cmd, (void *) result, 0x2a /* size */,
- SCSI_TIMEOUT, 3);
+ scsi_wait_req(sreq, scsi_cmd, result, 0x2a /* size */, SCSI_TIMEOUT, 3);
}
/**
@@ -354,10 +354,10 @@
* are copied to the Scsi_Device at @sreq->sr_device (sdev);
* any flags value is stored in *@bflags.
**/
-static void scsi_probe_lun(Scsi_Request *sreq, char *inq_result,
+static void scsi_probe_lun(struct scsi_request *sreq, char *inq_result,
int *bflags)
{
- Scsi_Device *sdev = sreq->sr_device; /* a bit ugly */
+ struct scsi_device *sdev = sreq->sr_device; /* a bit ugly */
unsigned char scsi_cmd[MAX_COMMAND_SIZE];
int possible_inq_resp_len;
@@ -522,7 +522,7 @@
* SCSI_SCAN_NO_RESPONSE: could not allocate or setup a Scsi_Device
* SCSI_SCAN_LUN_PRESENT: a new Scsi_Device was allocated and initialized
**/
-static int scsi_add_lun(Scsi_Device *sdev, char *inq_result, int *bflags)
+static int scsi_add_lun(struct scsi_device *sdev, char *inq_result, int *bflags)
{
struct scsi_device *sdev_sibling;
struct scsi_target *starget;
reply other threads:[~2003-06-03 20:52 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=20030603210538.GC9336@lst.de \
--to=hch@lst.de \
--cc=James.Bottomley@steeleye.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