From: Kay Sievers <kay.sievers@vrfy.org>
To: "'patman@aracnet.com'" <patman@aracnet.com>
Cc: "goggin, edward" <egoggin@emc.com>,
greg@kroah.com,
"'linux-hotplug-devel@lists.sourceforge.net'"
<linux-hotplug-devel@lists.sourceforge.net>,
"'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>,
christophe.varoqui@free.fr
Subject: Re: proposed update to scsi_id needing review
Date: Wed, 14 Sep 2005 20:24:47 +0200 [thread overview]
Message-ID: <20050914182447.GB16796@vrfy.org> (raw)
In-Reply-To: <20050914175548.GA20981@aracnet.com>
On Wed, Sep 14, 2005 at 10:55:48AM -0700, 'patman@aracnet.com' wrote:
> On Tue, Sep 13, 2005 at 12:48:43PM -0400, goggin, edward wrote:
> > Resending (original on June 9th) this patch notice after merging these
> > scsi_id changes into the version of scsi_id found in udev-068.
> >
> > This patch is to enable the use of scsi_id to derive a UID for a SCSI-2
> > device which is not compliant with the page 83 inquiry reply format for
> > either SPC-2 or SPC-3. In this case, the page 83 reply does not
> > contain a list of Identification descriptors but a single binary encoded
> > hexa-decimal Vendor Specified Identifier.
> >
> > The update is being driven by the need for scsi_id to support older
> > model EMC Symmetrix hardware, that is, models 4, 5, and 6.
>
> Ed - Looks good, I ran some simple tests (no EMC hardware here though).
>
> Greg or Kay, can you please apply Ed's patch?
Done!
Thanks,
Kay
next prev parent reply other threads:[~2005-09-14 18:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 16:48 proposed update to scsi_id needing review goggin, edward
2005-09-14 17:55 ` 'patman@aracnet.com'
2005-09-14 18:24 ` Kay Sievers [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-10 1:20 goggin, edward
2005-06-13 15:11 ` 'patman@aracnet.com'
2005-06-09 23:15 goggin, edward
2005-06-09 23:46 ` 'patman@aracnet.com'
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=20050914182447.GB16796@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=christophe.varoqui@free.fr \
--cc=egoggin@emc.com \
--cc=greg@kroah.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-scsi@vger.kernel.org \
--cc=patman@aracnet.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