From: Christoph Hellwig <hch@infradead.org>
To: "Elliott, Robert (Server Storage)" <Elliott@hp.com>
Cc: Spencer Baugh <sbaugh@catern.com>,
Christoph Hellwig <hch@infradead.org>,
"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
"open list:TARGET SUBSYSTEM" <linux-scsi@vger.kernel.org>,
"open list:TARGET SUBSYSTEM" <target-devel@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Joern Engel <joern@purestorage.com>,
Brian Bunker <brian@purestorage.com>
Subject: Re: [PATCH] target: add support for START_STOP_UNIT SCSI opcode
Date: Fri, 24 Jul 2015 23:32:19 -0700 [thread overview]
Message-ID: <20150725063219.GD26437@infradead.org> (raw)
In-Reply-To: <94D0CD8314A33A4D9D801C0FE68B40295AA06D79@G9W0745.americas.hpqcorp.net>
On Fri, Jul 24, 2015 at 03:06:12AM +0000, Elliott, Robert (Server Storage) wrote:
> Note that the officially published versions of the ISO and ANSI
> standards don't carry that revision number r36; they just have
> the standard name and year. SBC-3 revision 36 became
> "ANSI INCITS 514-2014 Information technology - SCSI Block
> Commands - 3 (SBC-3)".
>
> T10 isn't really obligated to keep making particular working
> drafts available, although the ones that have been assigned
> version descriptors (in SPC-n) are more likely to stick
> around. For SBC-3, only revisions 35 and 36 earned those.
Unfortunately the final T10 standards are only available for a high
monetary cost, so they aren't useful for Free Software development.
We work arounds this by referencing specific drafts that are available.
If T10 would regress even more by not providing them we'd have to find
other work arounds.
next prev parent reply other threads:[~2015-07-25 6:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 22:07 [PATCH] target: add support for START_STOP_UNIT SCSI opcode Spencer Baugh
2015-07-23 9:36 ` Christoph Hellwig
2015-07-23 22:27 ` Spencer Baugh
2015-07-24 3:06 ` Elliott, Robert (Server Storage)
2015-07-25 6:32 ` Christoph Hellwig [this message]
2015-07-31 6:58 ` Nicholas A. Bellinger
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=20150725063219.GD26437@infradead.org \
--to=hch@infradead.org \
--cc=Elliott@hp.com \
--cc=brian@purestorage.com \
--cc=joern@purestorage.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=sbaugh@catern.com \
--cc=target-devel@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