From: Doug Ledford <dledford@redhat.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] cpq driver compile fix
Date: Thu, 18 Jul 2002 21:05:13 -0400 [thread overview]
Message-ID: <20020718210513.B28235@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 310 bytes --]
This patch fixes the cpq driver's usage of sr_request (very trivial
actually). Please drop this in place and the cpq driver should start
working again. Thanks.
--
Doug Ledford <dledford@redhat.com> 919-754-3700 x44233
Red Hat, Inc.
1801 Varsity Dr.
Raleigh, NC 27606
[-- Attachment #2: cpq.patch --]
[-- Type: text/plain, Size: 2029 bytes --]
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet 1.630 -> 1.631
# drivers/scsi/cpqfcTSinit.c 1.16 -> 1.17
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 02/07/16 dledford@perf50.perf.redhat.com 1.631
# cpqfcTSinit.c:
# Fix usage of Scsi_Cmnd->request so it will compile.
# --------------------------------------------
#
diff -Nru a/drivers/scsi/cpqfcTSinit.c b/drivers/scsi/cpqfcTSinit.c
--- a/drivers/scsi/cpqfcTSinit.c Tue Jul 16 14:24:52 2002
+++ b/drivers/scsi/cpqfcTSinit.c Tue Jul 16 14:24:52 2002
@@ -475,7 +475,7 @@
{
struct request * req;
- req = &SCpnt->request;
+ req = SCpnt->request;
req->rq_status = RQ_SCSI_DONE; /* Busy, but indicate request done */
if (req->CPQFC_WAITING != NULL)
@@ -601,7 +601,7 @@
{
CPQFC_DECLARE_COMPLETION(wait);
- ScsiPassThruCmnd->request.CPQFC_WAITING = &wait;
+ ScsiPassThruCmnd->request->CPQFC_WAITING = &wait;
// eventually gets us to our own _quecommand routine
scsi_do_cmd( ScsiPassThruCmnd, &vendor_cmd->cdb[0],
buf,
@@ -611,7 +611,7 @@
// Other I/Os can now resume; we wait for our ioctl
// command to complete
CPQFC_WAIT_FOR_COMPLETION(&wait);
- ScsiPassThruCmnd->request.CPQFC_WAITING = NULL;
+ ScsiPassThruCmnd->request->CPQFC_WAITING = NULL;
}
result = ScsiPassThruCmnd->result;
@@ -1543,10 +1543,10 @@
SCpnt->SCp.buffers_residual = FCP_TARGET_RESET;
- SCpnt->request.CPQFC_WAITING = &wait;
+ SCpnt->request->CPQFC_WAITING = &wait;
scsi_do_cmd(SCpnt, scsi_cdb, NULL, 0, my_ioctl_done, timeout, retries);
CPQFC_WAIT_FOR_COMPLETION(&wait);
- SCpnt->request.CPQFC_WAITING = NULL;
+ SCpnt->request->CPQFC_WAITING = NULL;
}
/*
reply other threads:[~2002-07-19 1:02 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=20020718210513.B28235@redhat.com \
--to=dledford@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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