From: Vojtech Pavlik <vojtech@suse.cz>
To: linux-hotplug@vger.kernel.org
Subject: Re: IDs
Date: Sat, 29 Sep 2001 19:56:24 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-100179346711727@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100179008005789@msgid-missing>
On Sat, Sep 29, 2001 at 09:00:50PM +0200, Tim Jansen wrote:
> On Saturday 29 September 2001 20:04, you wrote:
> > Ok. Though I'd prefer PRODUCT;UNIQ;PHYS or PHYS;PRODUCT;UNIQ. Because
> > PRODUCT and UNIQ are bound together. UNIQ is only defined to be unique
> > in the PRODUCT class of devices, not globally.
>
> PHYS;PRODUCT;UNIQ is ok for me. It has the (very small) advantage that you
> can have any character in UNIQ, so you don't need to excape semicolons when
> you get the string from usb.
Ok.
> > There really is no reason to set the serial number taken from the SAPROM
> > on the PCI device ...
>
> In my old scheme there was no difference between the device itself and its
> functional units, this is why it was neccessary.
I see. I think this is cleaner design, though.
--
Vojtech Pavlik
SuSE Labs
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2001-09-29 19:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-29 19:00 IDs Tim Jansen
2001-09-29 19:56 ` Vojtech Pavlik [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-07 0:00 IDs Andries.Brouwer
2003-01-07 0:00 ` IDs Andries.Brouwer
2003-01-07 2:13 ` IDs Patrick Mansfield
2003-01-07 2:19 IDs Andries.Brouwer
2003-01-07 3:15 ` IDs Patrick Mansfield
2003-01-07 10:55 IDs Andries.Brouwer
2003-01-07 18:02 ` IDs Patrick Mansfield
2003-01-07 18:02 ` IDs Patrick Mansfield
2003-01-07 18:54 IDs Andries.Brouwer
2003-01-07 18:54 ` IDs Andries.Brouwer
2003-01-07 20:02 ` IDs Patrick Mansfield
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=marc-linux-hotplug-100179346711727@msgid-missing \
--to=vojtech@suse.cz \
--cc=linux-hotplug@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 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.