From: Greg KH <greg@kroah.com>
To: Kronos <kronos@kronoz.cjb.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Driver Core patches for 2.6.9
Date: Sat, 23 Oct 2004 13:34:04 -0700 [thread overview]
Message-ID: <20041023203404.GA24993@kroah.com> (raw)
In-Reply-To: <20041023202037.GA12345@dreamland.darkstar.lan>
On Sat, Oct 23, 2004 at 10:20:37PM +0200, Kronos wrote:
> Greg KH <greg@kroah.com> ha scritto:
> > ChangeSet 1.1867.3.4, 2004/09/15 11:36:09-07:00, greg@kroah.com
> >
> > kevent: standardize on the event types
> >
> > This prevents any potential typos from happening.
>
> [cut]
>
> > diff -Nru a/lib/kobject_uevent.c b/lib/kobject_uevent.c
> > --- a/lib/kobject_uevent.c 2004-10-19 09:22:44 -07:00
> > +++ b/lib/kobject_uevent.c 2004-10-19 09:22:44 -07:00
> > @@ -19,9 +19,29 @@
> > #include <linux/skbuff.h>
> > #include <linux/netlink.h>
> > #include <linux/string.h>
> > +#include <linux/kobject_uevent.h>
> > #include <linux/kobject.h>
> > #include <net/sock.h>
> >
> > +/*
> > + * These must match up with the values for enum kobject_action
> > + * as found in include/linux/kobject_uevent.h
> > + */
> > +static char *actions[] = {
> > + "add", /* 0x00 */
> > + "remove", /* 0x01 */
> > + "change", /* 0x02 */
> > + "mount", /* 0x03 */
> > +};
>
> Hi Greg,
> maybe it's just a matter of taste but I think that is better to do
> something like this:
>
> static char *actions[] = {
> [KOBJ_ADD] = "add",
> [KOBJ_REMOVE] = "remove",
> [KOBJ_CHANGE] = "change",
> [KOBJ_MOUNT] = "mount",
> };
>
> This would prevent the insertion of a new action in the wrong place.
See the following patches in the series, which fixes this up :)
thanks,
greg k-h
next prev parent reply other threads:[~2004-10-23 20:36 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 16:34 [BK PATCH] " Greg KH
2004-10-19 16:35 ` [PATCH] " Greg KH
2004-10-19 16:35 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:36 ` Greg KH
2004-10-19 16:37 ` Greg KH
2004-10-19 16:37 ` Greg KH
2004-10-19 16:37 ` Greg KH
2004-10-19 16:37 ` Greg KH
2004-10-19 16:37 ` Greg KH
2004-10-19 16:37 ` Greg KH
2004-10-23 20:20 ` Kronos
2004-10-23 20:34 ` Greg KH [this message]
2004-10-23 21:46 ` Kronos
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=20041023203404.GA24993@kroah.com \
--to=greg@kroah.com \
--cc=kronos@kronoz.cjb.net \
--cc=linux-kernel@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
Powered by JetHome