From: Patrick Mansfield <patmans@us.ibm.com>
To: Luben Tuikov <luben@splentec.com>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH] 2.5.x alternate add back missing scsi_queue_next_request calls
Date: Fri, 21 Mar 2003 16:24:21 -0800 [thread overview]
Message-ID: <20030321162421.A9398@beaverton.ibm.com> (raw)
In-Reply-To: <3E7B97A0.4010204@splentec.com>; from luben@splentec.com on Fri, Mar 21, 2003 at 05:52:16PM -0500
On Fri, Mar 21, 2003 at 05:52:16PM -0500, Luben Tuikov wrote:
> All those users of scsi_put_command() DO NOT need to call
> scsi_queue_next_request().
>
> For this reason you do not need to export it.
OK ... new version in a few minutes.
> cpqfcTSinit.c -- needs a scsi command to reset the device -- called
> from the eh_handler.
Not exactly but the driver does't compile as it uses scsi_do_cmd, and is
commented as needing a switch to Scsi_Request, so:
OK.
> aha152x.c -- needs a scsi command to reset the device -- called
> from the eh_handler.
OK
> gdth.c -- flushing and releasing the device.
OK. The driver is also broken, still using scsi_do_cmd.
> gdth_proc.c -- same.
It's a proc interface to get or set info, but again it is broken using
scsi_do_cmd, so also:
OK.
> ONLY because they notify via scsi_done(command), but entered via
> scsi_request! This needs a patch. See my previous post.
>
> I.e. we need a patch which fixes this infrastructre, rather than
> a patchwork solution. (Address at the root.)
No one disagrees with fixing up the code, but it takes time. You don't
have to repeat this point in every post.
-- Patrick Mansfield
next prev parent reply other threads:[~2003-03-22 0:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-21 22:15 [PATCH] 2.5.x alternate add back missing scsi_queue_next_request calls Patrick Mansfield
2003-03-21 22:52 ` Luben Tuikov
2003-03-22 0:24 ` Patrick Mansfield [this message]
2003-03-22 0:40 ` [PATCH] 2.5.x 3rd version add " Patrick Mansfield
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=20030321162421.A9398@beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=James.Bottomley@steeleye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=luben@splentec.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