From: Roman Kagan <Roman.Kagan@itep.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: [udev] don't rely on field order in namedev_parse
Date: Wed, 17 Dec 2003 17:04:29 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-107168096016549@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-107152798528161@msgid-missing>
Hi,
On Tue, Dec 16, 2003 at 02:36:25AM +0100, Kay Sievers wrote:
> 01-remove-field-ordering.diff
> [...]
> diff -Nru a/namedev_parse.c b/namedev_parse.c
> --- a/namedev_parse.c Tue Dec 16 02:26:49 2003
> +++ b/namedev_parse.c Tue Dec 16 02:26:49 2003
> @@ -169,13 +156,8 @@
> if (temp = NULL)
> goto exit;
> lineno++;
> -
> dbg_parse("read '%s'", temp);
>
> - /* eat the whitespace at the beginning of the line */
> - while (isspace(*temp))
> - ++temp;
> -
> /* empty line? */
> if (*temp = 0x00)
> continue;
> @@ -184,199 +166,160 @@
> if (*temp = COMMENT_CHARACTER)
> continue;
>
> + /* eat the whitespace */
> + while (isspace(*temp))
> + ++temp;
> +
> memset(&dev, 0x00, sizeof(struct config_device));
>
This chunk broke parsing of blank lines and comments with blanks before
'#'. Please revert it with the patch below.
Roman.
--- udev-009/namedev_parse.c~ 2003-12-16 05:26:49.000000000 +0300
+++ udev-009/namedev_parse.c 2003-12-17 20:00:21.000000000 +0300
@@ -158,6 +158,10 @@
lineno++;
dbg_parse("read '%s'", temp);
+ /* eat the whitespace */
+ while (isspace(*temp))
+ ++temp;
+
/* empty line? */
if (*temp = 0x00)
continue;
@@ -166,10 +170,6 @@
if (*temp = COMMENT_CHARACTER)
continue;
- /* eat the whitespace */
- while (isspace(*temp))
- ++temp;
-
memset(&dev, 0x00, sizeof(struct config_device));
/* get the method */
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
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 prev parent reply other threads:[~2003-12-17 17:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 22:36 [udev] don't rely on field order in namedev_parse Greg KH
2003-12-16 0:21 ` Kay Sievers
2003-12-16 0:27 ` Greg KH
2003-12-16 1:36 ` Kay Sievers
2003-12-16 23:40 ` Greg KH
2003-12-17 0:50 ` Kay Sievers
2003-12-17 0:59 ` Greg KH
2003-12-17 17:04 ` Roman Kagan [this message]
2003-12-17 18:26 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2003-12-12 19:36 Kay Sievers
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-107168096016549@msgid-missing \
--to=roman.kagan@itep.ru \
--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).