From: Luben Tuikov <luben@splentec.com>
To: linux-scsi@vger.kernel.org
Subject: [PATCH] SCSI Core cmd->{lun, target, channel} ==> cmd->device->{lun, id, channel} 1/3
Date: Mon, 06 Jan 2003 19:49:39 -0500 [thread overview]
Message-ID: <3E1A2423.7080500@splentec.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1419 bytes --]
This patch makes all of SCSI Core and LLDD use cmd->device->{lun, id, channel},
instead of the old cmd->{lun, target, channel}.
The new aic7xxx series driver has been partially converted. The problem is:
drivers/scsi/aic7xxx/aic79xx_osm.c: In function `ahd_linux_dv_fill_cmd':
drivers/scsi/aic7xxx/aic79xx_osm.c:3304: structure has no member named `host'
drivers/scsi/aic7xxx/aic79xx_osm.c:3306: structure has no member named `target'
drivers/scsi/aic7xxx/aic79xx_osm.c:3307: structure has no member named `lun'
drivers/scsi/aic7xxx/aic79xx_osm.c:3308: structure has no member named `channel'
and the same thing in:
drivers/scsi/aic7xxx/aic7xxx_osm.c: In function `ahc_linux_dv_fill_cmd':
drivers/scsi/aic7xxx/aic7xxx_osm.c:3154: structure has no member named `host'
drivers/scsi/aic7xxx/aic7xxx_osm.c:3156: structure has no member named `target'
drivers/scsi/aic7xxx/aic7xxx_osm.c:3157: structure has no member named `lun'
drivers/scsi/aic7xxx/aic7xxx_osm.c:3158: structure has no member named `channel'
cpqfsTSinit.c has a 2 line problem quite similar to the aic7xxx above.
All drivers have been converted, even the ones which do not complie and need
to be converted to the newer DMA API.
--
Luben
P.S. This is a resent mail. In the first email, the patch was inserted
in the body of the mail text, all 170 KiB of it and chances are that
you didn't get it -- neither did I. Now it's a gzipped attachment.
[-- Attachment #2: ch_tar_lun_all54.patch.gz --]
[-- Type: application/x-gzip, Size: 40373 bytes --]
reply other threads:[~2003-01-07 0:49 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=3E1A2423.7080500@splentec.com \
--to=luben@splentec.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