From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: [udev] namedev.c - change order of fields in CALLOUT
Date: Thu, 20 Nov 2003 22:05:53 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-106936599009984@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 471 bytes --]
Hi Greg,
I want to bring the CALLOUT field ordering in line with the other
methods, cause the current parsing relies on the ordering it's good
to have it like the others. The BUS= is now the first expected field.
Also made the last two remaining field names to uppercase and the man page
callout example is updated.
thanks,
Kay
10-namedev.c-callout-fields-order.diff
10-udev.8-callout-fields-order.diff
namedev.c - reorder CALLOUT fields to match the other methods
[-- Attachment #2: 10-namedev.c-callout-fields-order.diff --]
[-- Type: text/plain, Size: 1223 bytes --]
--- ../udev/namedev.c 2003-11-20 22:07:06.000000000 +0100
+++ namedev.c 2003-11-20 22:59:27.000000000 +0100
@@ -286,7 +286,7 @@
/* ID="id" */
temp2 = strsep(&temp, ",");
- retval = get_value("id", &temp, &temp3);
+ retval = get_value("ID", &temp, &temp3);
if (retval)
break;
strfieldcpy(dev.id, temp3);
@@ -314,7 +314,7 @@
/* PLACE="place" */
temp2 = strsep(&temp, ",");
- retval = get_value("place", &temp, &temp3);
+ retval = get_value("PLACE", &temp, &temp3);
if (retval)
break;
strfieldcpy(dev.place, temp3);
@@ -353,18 +353,18 @@
/* number type */
dev.type = CALLOUT;
- /* PROGRAM="executable" */
- retval = get_value("PROGRAM", &temp, &temp3);
+ /* BUS="bus" */
+ retval = get_value("BUS", &temp, &temp3);
if (retval)
break;
- strfieldcpy(dev.exec_program, temp3);
+ strfieldcpy(dev.bus, temp3);
- /* BUS="bus" */
+ /* PROGRAM="executable" */
temp2 = strsep(&temp, ",");
- retval = get_value("BUS", &temp, &temp3);
+ retval = get_value("PROGRAM", &temp, &temp3);
if (retval)
break;
- strfieldcpy(dev.bus, temp3);
+ strfieldcpy(dev.exec_program, temp3);
/* ID="id" */
temp2 = strsep(&temp, ",");
[-- Attachment #3: 10-udev.8-callout-fields-order.diff --]
[-- Type: text/plain, Size: 491 bytes --]
--- ../udev/udev.8 2003-11-20 22:07:06.000000000 +0100
+++ udev.8 2003-11-20 22:23:50.000000000 +0100
@@ -105,7 +105,7 @@
REPLACE, KERNEL="ttyUSB1", NAME="pda"
# if /sbin/scsi_id returns "OEM 0815" device will be called disk1
-CALLOUT, PROGRAM="/sbin/scsi_id" BUS="scsi", ID="OEM 0815" NAME="disk1"
+CALLOUT, BUS="scsi", PROGRAM="/sbin/scsi_id", ID="OEM 0815", NAME="disk1"
# USB webcams to be called webcam0, webcam1, ...
LABEL, BUS="usb", model="WebCam Version 3", NAME="webcam%n"
next reply other threads:[~2003-11-20 22:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 22:05 Kay Sievers [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-21 3:26 [udev] namedev.c - change order of fields in CALLOUT Arnd Bergmann
2003-11-21 6:49 ` Greg KH
2003-11-21 17:08 ` Kay Sievers
2003-11-23 6:01 ` Greg KH
2003-11-23 6:03 ` 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=marc-linux-hotplug-106936599009984@msgid-missing \
--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).