From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: [PATCH] clarify udevinfo device walk
Date: Mon, 01 Mar 2004 23:52:37 +0000 [thread overview]
Message-ID: <20040301235237.GC6332@vrfy.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 125 bytes --]
It seems that the long attribute list can confuse the user.
Se here we print a few words on top the attributes.
thanks,
Kay
[-- Attachment #2: 01-clarify-device-walk.patch --]
[-- Type: text/plain, Size: 814 bytes --]
===== udevinfo.c 1.14 vs edited =====
--- 1.14/udevinfo.c Wed Feb 25 01:04:14 2004
+++ edited/udevinfo.c Tue Mar 2 00:46:03 2004
@@ -148,7 +148,14 @@
retval = -1;
goto exit;
}
- printf("\ndevice '%s' has major:minor %s", class_dev->path, attr->value);
+
+ printf("\nudevinfo starts with the device the node belongs to and then walks up the\n"
+ "device chain to print for every device found all possibly useful attributes\n"
+ "in the udev key format.\n"
+ "Only attributes within one device section may be used in a rule to match the\n"
+ "device for which the node will be created.\n"
+ "\n");
+ printf("device '%s' has major:minor %s", class_dev->path, attr->value);
sysfs_close_attribute(attr);
/* open sysfs class device directory and print all attributes */
next reply other threads:[~2004-03-01 23:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 23:52 Kay Sievers [this message]
2004-03-02 0:09 ` [PATCH] clarify udevinfo device walk Greg KH
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=20040301235237.GC6332@vrfy.org \
--to=kay.sievers@vrfy.org \
--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).