From: Patrick Mansfield <patmans@us.ibm.com>
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net,
mdharm-kernel@one-eyed-alien.net, zwane@holomorphy.com
Subject: Re: IDs
Date: Mon, 6 Jan 2003 19:15:22 -0800 [thread overview]
Message-ID: <20030106191522.A11624@beaverton.ibm.com> (raw)
In-Reply-To: <UTC200301070219.h072JjD19965.aeb@smtp.cwi.nl>; from Andries.Brouwer@cwi.nl on Tue, Jan 07, 2003 at 03:19:45AM +0100
On Tue, Jan 07, 2003 at 03:19:45AM +0100, Andries.Brouwer@cwi.nl wrote:
> > We can tell if the id sdev->name should be unique by looking at
> > the first byte (it is not unique if the value is 'Z'),
> > SCSI_UID_UNKNOWN.
>
> Such things are nontrivial.
Yes ...
> And where we have heuristics only, it cannot be "wrong"
> to truncate at 50 positions or so. The heuristic does
> not become appreciably weaker.
But, we don't have to truncate, we should just allocate as many bytes as
we need, and store the information.
And, the sysfs name should not store the id.
-- Patrick Mansfield
next prev parent reply other threads:[~2003-01-07 3:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-07 2:19 IDs Andries.Brouwer
2003-01-07 3:15 ` Patrick Mansfield [this message]
2003-01-07 10:55 ` IDs Andries.Brouwer
2003-01-07 17:07 ` IDs Greg KH
2003-01-07 17:07 ` [linux-usb-devel] " Greg KH
2003-01-07 18:02 ` IDs Patrick Mansfield
2003-01-07 18:02 ` IDs Patrick Mansfield
-- strict thread matches above, loose matches on Subject: below --
2003-01-07 18:54 IDs Andries.Brouwer
2003-01-07 18:54 ` IDs Andries.Brouwer
2003-01-07 20:02 ` IDs Patrick Mansfield
2003-01-07 0:00 IDs Andries.Brouwer
2003-01-07 0:00 ` IDs Andries.Brouwer
2003-01-07 2:13 ` IDs Patrick Mansfield
2001-09-29 19:00 IDs Tim Jansen
2001-09-29 19:56 ` IDs Vojtech Pavlik
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=20030106191522.A11624@beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mdharm-kernel@one-eyed-alien.net \
--cc=zwane@holomorphy.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.