From: Olaf Hering <olh@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] allow to specify node permissions in the rule
Date: Fri, 12 Mar 2004 11:30:20 +0000 [thread overview]
Message-ID: <20040312113020.GA6067@suse.de> (raw)
In-Reply-To: <20040307011223.GA22054@vrfy.org>
On Fri, Mar 12, Kay Sievers wrote:
> On Fri, 2004-03-12 at 11:43, Olaf Hering wrote:
> > On Sun, Mar 07, Kay Sievers wrote:
> > > + dev->kernel, dev->program, dev->result,;
> > > + dev->owner, dev->group, dev->mode);
> >
> > gcc is very unhappy about that extra ';' :)
>
> Oh yes, thanks.
> How did you find this? I don't get any warning.
namedev_parse.c: In function `dump_config_dev':
namedev_parse.c:62: error: parse error before ';' token
namedev_parse.c:62: warning: left-hand operand of comma expression has no effect
namedev_parse.c:62: warning: left-hand operand of comma expression has no effect
namedev_parse.c:62: error: parse error before ')' token
--
USB is for mice, FireWire is for men!
sUse lINUX ag, n√úRNBERG
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&opÃk
_______________________________________________
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:[~2004-03-12 11:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-07 1:12 [PATCH] allow to specify node permissions in the rule Kay Sievers
2004-03-10 22:41 ` Greg KH
2004-03-11 2:18 ` Kay Sievers
2004-03-12 1:07 ` Greg KH
2004-03-12 2:20 ` Kay Sievers
2004-03-12 10:43 ` Olaf Hering
2004-03-12 11:19 ` Kay Sievers
2004-03-12 11:30 ` Olaf Hering [this message]
2004-03-12 11:35 ` Kay Sievers
2004-03-12 16:43 ` Greg KH
2004-03-12 17:44 ` 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=20040312113020.GA6067@suse.de \
--to=olh@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.