From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: [PATCH] clarify udevinfo text
Date: Thu, 04 Mar 2004 03:33:08 +0000 [thread overview]
Message-ID: <20040304033308.GB15363@vrfy.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 121 bytes --]
Make udevinfo attribute printing note so clear,
that's nearly impossible to misunderstand it in the future.
thanks,
Kay
[-- Attachment #2: 02-clarify-udevinfo.patch --]
[-- Type: text/plain, Size: 889 bytes --]
===== udevinfo.c 1.17 vs edited =====
--- 1.17/udevinfo.c Wed Mar 3 22:41:52 2004
+++ edited/udevinfo.c Thu Mar 4 04:22:21 2004
@@ -151,10 +151,10 @@
}
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"
+ "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"
+ "Only attributes within one device section may be used together in one rule,\n"
+ "to match the 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);
next reply other threads:[~2004-03-04 3:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 3:33 Kay Sievers [this message]
2004-03-04 19:02 ` [PATCH] clarify udevinfo text 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=20040304033308.GB15363@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).