From: Patrick Mansfield <patmans@us.ibm.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
Jens Axboe <axboe@suse.de>
Subject: Re: [GIT PATCH] SCSI merge for 2.6.13
Date: Wed, 7 Sep 2005 10:47:44 -0700 [thread overview]
Message-ID: <20050907174744.GA13172@us.ibm.com> (raw)
In-Reply-To: <1126053452.5012.28.camel@mulgrave>
On Tue, Sep 06, 2005 at 07:37:32PM -0500, James Bottomley wrote:
> This should be the entire contents of the SCSI tree I've been saving.
> It also includes Jens' send SCSI requests via bios tree that he, Mike
> Christie and I have been working on.
>
> The patch is available here:
>
> master.kernel.org:/pub/linux/kernel/scm/jejb/scsi-for-linus-2.6.git
>
> o convert ch to use scsi_execute_req
> o convert sr to scsi_execute_req
> o convert sd to scsi_execute_req (and update the scsi_execute_req API)
> o convert SPI transport class to scsi_execute
> o convert the remaining mid-layer pieces to scsi_execute_req
The scsi_execute() retries argument is still not used.
How is this going to work?
For example, multiple unit attentions (power on / reset) during scanning.
We send REPORT LUN, READ CAPACITY, etc., and would not retry if we got a
unit attention.
-- Patrick Mansfield
next prev parent reply other threads:[~2005-09-07 17:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 0:37 [GIT PATCH] SCSI merge for 2.6.13 James Bottomley
2005-09-07 17:47 ` Patrick Mansfield [this message]
2005-09-07 18:14 ` James Bottomley
2005-09-07 19:35 ` Jens Axboe
2005-09-08 0:31 ` Linus Torvalds
2005-09-08 0:40 ` James Bottomley
2005-09-08 0:41 ` Linus Torvalds
2005-09-08 0:49 ` Linus Torvalds
2005-09-08 0:56 ` James Bottomley
2005-09-08 0:59 ` Andrew Morton
2005-09-08 0:53 ` James Bottomley
-- strict thread matches above, loose matches on Subject: below --
2005-09-13 2:44 [GIT PATCH] scsi " 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=20050907174744.GA13172@us.ibm.com \
--to=patmans@us.ibm.com \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.