All of lore.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dgilbert@interlog.com>
To: Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@suse.de>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	linux-scsi@vger.kernel.org,
	James Bottomley <james.bottomley@hansenpartnership.com>,
	Hannes Reinecke <hare@suse.com>
Subject: Re: [PATCH] scsi: vpd pages are mandatory for SPC-2
Date: Tue, 15 Mar 2016 18:19:21 +0100	[thread overview]
Message-ID: <56E84419.3040109@interlog.com> (raw)
In-Reply-To: <20160315074232.GA10944@lst.de>

On 16-03-15 08:42 AM, Christoph Hellwig wrote:
> On Tue, Mar 15, 2016 at 08:28:42AM +0100, Hannes Reinecke wrote:
>> But it feels even sillier having to whitelist every
>> standards-conformant device here; I certainly was when I figured
>> that EMC Clariion won't work properly without this patch.
>>
>> And the idea was to mark off _misbehaving_ drives, not the other way
>> round.
>
> It's the idea, but it has to prove workable as well in the end.
>
> That being said I'd prefer to allow Hannes patch in and see what
> the fallout is.

I don't have many drafts archived for SPC-2 but the two that I do have:
    spc2r18.pdf [20000521]
    spc2r20.pdf [20010718]

indicate that those two VPD pages were made mandatory right at the
end of the draft cycle for SPC-2. spc2r20.pdf was the last draft
prior to the standard and it does show them as mandatory in table 185
on page 218. The corresponding table in spc2r18.pdf does not have
a column indicating whether the listed VPD pages are mandatory or
not (or words that I can find in the description of VPD pages 0x0
and 0x83 to suggest they are mandatory).

Doug Gilbert

  reply	other threads:[~2016-03-15 17:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-11 13:46 [PATCH] scsi: vpd pages are mandatory for SPC-2 Hannes Reinecke
2016-03-14 23:37 ` Martin K. Petersen
2016-03-15  7:28   ` Hannes Reinecke
2016-03-15  7:42     ` Christoph Hellwig
2016-03-15 17:19       ` Douglas Gilbert [this message]
2016-03-16  8:12         ` Hannes Reinecke
2016-03-15 21:36     ` Martin K. Petersen
2016-03-16  7:38       ` Hannes Reinecke
2016-03-16  7:47         ` Hannes Reinecke
2016-03-23 21:02 ` Martin K. Petersen

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=56E84419.3040109@interlog.com \
    --to=dgilbert@interlog.com \
    --cc=hare@suse.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=james.bottomley@hansenpartnership.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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 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.