From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: device not part of a subsystem?
Date: Sat, 09 Apr 2005 00:01:29 +0000 [thread overview]
Message-ID: <20050409000129.GA32481@wonderland.linux.it> (raw)
[-- Attachment #1: Type: text/plain, Size: 393 bytes --]
Is this a bug? The rfcomm driver reports just this:
$ udevinfo -a -p /class/tty/rfcomm0
[...]
device '/sys/class/tty/rfcomm0' has major:minor 216:0
looking at class device '/sys/class/tty/rfcomm0':
SYSFS{dev}="216:0"
Should I change my rules files to not depend on the driver being part of
the tty subsystem or ask for the rfcomm driver to be fixed?
--
ciao,
Marco
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-04-09 0:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-09 0:01 Marco d'Itri [this message]
2005-04-09 0:14 ` device not part of a subsystem? Kay Sievers
2005-04-09 0:29 ` Marco d'Itri
2005-04-09 9:20 ` Kay Sievers
2005-04-09 9:22 ` Marco d'Itri
2005-04-09 15:52 ` Marco d'Itri
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=20050409000129.GA32481@wonderland.linux.it \
--to=md@linux.it \
--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).