From: Finn Thain <fthain@telegraphics.com.au>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Douglas Gilbert <dgilbert@interlog.com>,
Damien Le Moal <damien.lemoal@wdc.com>,
linux-scsi@vger.kernel.org,
"Martin K . Petersen" <martin.petersen@oracle.com>,
linux-usb@vger.kernel.org, usb-storage@lists.one-eyed-alien.net,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Justin Piszcz <jpiszcz@lucidpixels.com>
Subject: Re: [PATCH 0/2] Fix SCSI & USB Storage CHECK CONDITION handling
Date: Sat, 28 Sep 2019 09:33:59 +1000 (AEST) [thread overview]
Message-ID: <alpine.LNX.2.21.1909280906530.76@nippy.intranet> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1909271004470.1698-100000@iolanthe.rowland.org>
[snipped selective measurements of word usage]
On Fri, 27 Sep 2019, Alan Stern wrote:
>
> So I guess this was never defined precisely.
>
The O.E.D. defines these terms:
residual
a. [...]
n. 1. a quantity remaining after other things have been subtracted
or allowed for. [...]
2. [...]
3. [...]
and
residue
n. a small amount of something that remains after the main part
has gone or been taken or used.
So, writing "residue" could be misleading as the connotation is that the
remaining part is the lesser part.
I think that's probably why the term "residual" gets used in finance (and
in SCSI transfers).
--
prev parent reply other threads:[~2019-09-27 23:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 22:08 [PATCH 0/2] Fix SCSI & USB Storage CHECK CONDITION handling Damien Le Moal
2019-09-26 22:08 ` [PATCH 1/2] scsi: save/restore command resid for error handling Damien Le Moal
2019-09-27 19:20 ` Christoph Hellwig
2019-09-26 22:08 ` [PATCH 2/2] usb: Clear scsi command resid when residue is 0 Damien Le Moal
2019-09-26 23:57 ` [PATCH 0/2] Fix SCSI & USB Storage CHECK CONDITION handling Alan Stern
2019-09-27 0:17 ` Damien Le Moal
2019-09-27 16:34 ` Alan Stern
2019-09-27 20:51 ` Damien Le Moal
2019-09-27 0:54 ` Douglas Gilbert
2019-09-27 14:11 ` Alan Stern
2019-09-27 23:33 ` Finn Thain [this message]
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=alpine.LNX.2.21.1909280906530.76@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=damien.lemoal@wdc.com \
--cc=dgilbert@interlog.com \
--cc=gregkh@linuxfoundation.org \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage@lists.one-eyed-alien.net \
/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;
as well as URLs for NNTP newsgroup(s).