From: Christoph Hellwig <hch@infradead.org>
To: Mike Christie <mikenc@us.ibm.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] fixes compile errors in cpqfcTS driver
Date: Tue, 22 Apr 2003 07:44:15 +0100 [thread overview]
Message-ID: <20030422074414.A26090@infradead.org> (raw)
In-Reply-To: <3EA48555.8020600@us.ibm.com>; from mikenc@us.ibm.com on Mon, Apr 21, 2003 at 04:57:09PM -0700
On Mon, Apr 21, 2003 at 04:57:09PM -0700, Mike Christie wrote:
> + Scsi_Device DumSdev;
Please use struct scsi_device in any new code.
> int Chan, Targ, i;
> struct info_str info;
> CPQFCHBA *cpqfcHBA;
> @@ -963,11 +964,12 @@ int cpqfcTS_proc_info (char *buffer, cha
>
> #define DISPLAY_WWN_INFO
> #ifdef DISPLAY_WWN_INFO
> + DumCmnd.device = &DumSdev;
I don't think the onstack command/device will work anymore.
You'll have to use scsi_get_command/scsi_put_command I guess
next prev parent reply other threads:[~2003-04-22 6:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-21 23:57 [PATCH] fixes compile errors in cpqfcTS driver Mike Christie
2003-04-22 6:44 ` Christoph Hellwig [this message]
2003-04-22 13:54 ` James Bottomley
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=20030422074414.A26090@infradead.org \
--to=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mikenc@us.ibm.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