From: Eric Dumazet <eric.dumazet@gmail.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: ebiederm@aristanetworks.com, randy.dunlap@oracle.com,
gregkh@suse.de, linux-kernel@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH] kobject: Suppress compiler warning with gcc 3.x
Date: Thu, 03 Jun 2010 07:31:41 +0200 [thread overview]
Message-ID: <1275543101.29413.76.camel@edumazet-laptop> (raw)
In-Reply-To: <201006030523.o535NA16029042@www262.sakura.ne.jp>
Le jeudi 03 juin 2010 à 14:23 +0900, Tetsuo Handa a écrit :
> Gcc 3.x generates a warning
>
> include/linux/sysfs.h:183: warning: parameter has incomplete type
>
> on each file.
> Suppress the warning by moving the definition of "enum kobj_ns_type"
> to before "#include <linux/sysfs.h>".
>
> Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
I was about to submit same patch, but I was also reverting 27eabc7cb4b3
(sysfs: Don't use enums in inline function declaration.)
So that sysfs_exit_ns() prototype is consistent regardless of
CONFIG_SYSFS
What do you think ?
> ---
> include/linux/kobject.h | 20 ++++++++++----------
> 1 file changed, 10 insertions(+), 10 deletions(-)
>
> --- linux-2.6.35-rc1.orig/include/linux/kobject.h
> +++ linux-2.6.35-rc1/include/linux/kobject.h
> @@ -16,6 +16,16 @@
> #ifndef _KOBJECT_H_
> #define _KOBJECT_H_
>
> +/*
> + * Namespace types which are used to tag kobjects and sysfs entries.
> + * Network namespace will likely be the first.
> + */
> +enum kobj_ns_type {
> + KOBJ_NS_TYPE_NONE = 0,
> + KOBJ_NS_TYPE_NET,
> + KOBJ_NS_TYPES
> +};
> +
> #include <linux/types.h>
> #include <linux/list.h>
> #include <linux/sysfs.h>
> @@ -136,16 +146,6 @@ struct kobj_attribute {
>
> extern const struct sysfs_ops kobj_sysfs_ops;
>
> -/*
> - * Namespace types which are used to tag kobjects and sysfs entries.
> - * Network namespace will likely be the first.
> - */
> -enum kobj_ns_type {
> - KOBJ_NS_TYPE_NONE = 0,
> - KOBJ_NS_TYPE_NET,
> - KOBJ_NS_TYPES
> -};
> -
> struct sock;
>
> /*
next prev parent reply other threads:[~2010-06-03 5:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 5:23 Tetsuo Handa
2010-06-03 5:31 ` Eric Dumazet [this message]
2010-06-03 5:55 ` Américo Wang
2010-06-03 6:02 ` Eric W. Biederman
2010-06-03 6:23 ` Américo Wang
2010-06-03 6:40 ` Eric W. Biederman
2010-06-03 8:57 ` Américo Wang
2010-06-03 9:32 ` Eric Dumazet
2010-06-03 6:46 ` Eric Dumazet
2010-06-03 8:52 ` Américo Wang
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=1275543101.29413.76.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=ebiederm@aristanetworks.com \
--cc=ebiederm@xmission.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=randy.dunlap@oracle.com \
/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
all inboxes | Powered by JetHome®