From: Tim Jansen <tim@tjansen.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: IDs
Date: Sat, 29 Sep 2001 19:00:50 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-100179008005789@msgid-missing> (raw)
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.
> 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.
bye...
_______________________________________________
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 reply other threads:[~2001-09-29 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-29 19:00 Tim Jansen [this message]
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=marc-linux-hotplug-100179008005789@msgid-missing \
--to=tim@tjansen.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).