From: James Bottomley <James.Bottomley@SteelEye.com>
To: Douglas Gilbert <dougg@torque.net>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>, bunk@fs.tum.de
Subject: Re: Is scsi_cmnd::underflow still useful?
Date: 12 Jul 2004 19:55:13 -0500 [thread overview]
Message-ID: <1089680114.2074.198.camel@mulgrave> (raw)
In-Reply-To: <40F2E93B.3040607@torque.net>
On Mon, 2004-07-12 at 14:40, Douglas Gilbert wrote:
> Doesn't look like many LLDs act on scsi_cmnd::underflow.
> Seems to me that scsi_cmnd::resid is a more general
> replacement.
well, I know I suggested a recent use of it to the USB people , so I
don't think it's entirely unused. resid can't be a replacement because
they mean different things:
resid - number of bytes left over after a transaction
underflow - driver must return error if less than this amount
transferred.
James
next prev parent reply other threads:[~2004-07-13 0:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 19:40 Is scsi_cmnd::underflow still useful? Douglas Gilbert
2004-07-13 0:55 ` James Bottomley [this message]
2004-07-13 5:09 ` Matthew Dharm
2004-07-13 22:09 ` Douglas Gilbert
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=1089680114.2074.198.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=bunk@fs.tum.de \
--cc=dougg@torque.net \
--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