From: ebiederm@xmission.com (Eric W. Biederman)
To: Greg KH <gregkh@suse.de>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: linux-next: Tree for April 30 (CONFIG_SYSFS=n)
Date: Wed, 05 May 2010 14:35:03 -0700 [thread overview]
Message-ID: <m1d3xa1188.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <20100505162459.GA20296@suse.de> (Greg KH's message of "Wed\, 5 May 2010 09\:24\:59 -0700")
Greg KH <gregkh@suse.de> writes:
> On Wed, May 05, 2010 at 09:17:38AM -0700, Randy Dunlap wrote:
>> On Fri, 30 Apr 2010 10:50:16 -0700 Randy Dunlap wrote:
>>
>> > On Fri, 30 Apr 2010 16:35:38 +1000 Stephen Rothwell wrote:
>> >
>> > > Hi all,
>> > >
>> > > Changes since 20100429:
>> >
>> >
>> > When CONFIG_SYSFS is disabled:
>> >
>> > include/linux/sysfs.h:330: error: parameter 1 ('type') has incomplete type
>>
>>
>> Still have this in linux-next of May 5-2010.
>
> Eric, this is due to your changes, care to fix it up?
Apologies for not looking at this earlier. I just took a look
at this and I believe this error is the result of a gcc bug.
This appears to the fragment that doesn't compile.
enum kobj_ns_type;
static inline void sysfs_exit_ns(enum kobj_ns_type type, const void *tag)
{
}
I could either include kobject.h or make the fragment:
static inline void sysfs_exit_ns(int type, const void *tag)
{
}
I really don't like either option.
Does anyone know how to smack gcc up the side of the head and convince
it has all of the information it needs, and get it to stop complaining?
Eric
next prev parent reply other threads:[~2010-05-05 21:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 6:35 linux-next: Tree for April 30 Stephen Rothwell
2010-04-30 17:50 ` linux-next: Tree for April 30 (CONFIG_SYSFS=n) Randy Dunlap
2010-05-05 16:17 ` Randy Dunlap
2010-05-05 16:24 ` Greg KH
2010-05-05 21:35 ` Eric W. Biederman [this message]
2010-05-05 21:54 ` [PATCH] sysfs: Don't use enums in inline function declaration Eric W. Biederman
2010-05-05 22:05 ` Randy Dunlap
2010-04-30 19:27 ` linux-next: Tree for April 30 Frederic Weisbecker
2010-05-03 7:29 ` Stephen Rothwell
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=m1d3xa1188.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
/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.