public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Greg KH <gregkh@suse.de>
Cc: dhowells@redhat.com, ebiederm@xmission.com,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Break the kobject namespace defs into their own header
Date: Thu, 12 Aug 2010 12:56:25 +0100	[thread overview]
Message-ID: <12812.1281614185@redhat.com> (raw)
In-Reply-To: <20100811150746.GA9070@suse.de>

Greg KH <gregkh@suse.de> wrote:

> What "ordering problem" is there?  I don't see a build error here, do
> you?

Yes:

  CC      arch/mn10300/kernel/asm-offsets.s
In file included from include/linux/kobject.h:21,
                 from include/linux/sched.h:91,
                 from arch/mn10300/kernel/asm-offsets.c:7:
include/linux/sysfs.h:177: warning: parameter 1 ('type') has incomplete type
  GEN     include/generated/asm-offsets.h
  CALL    scripts/checksyscalls.sh
<stdin>:1526:2: warning: #warning syscall fanotify_init not implemented
<stdin>:1530:2: warning: #warning syscall fanotify_mark not implemented
<stdin>:1534:2: warning: #warning syscall prlimit64 not implemented
  CC      init/main.o
  CC      arch/mn10300/mm/init.o
  CC      arch/mn10300/kernel/process.o
In file included from include/linux/kobject.h:21,
                 from include/linux/sched.h:91,
                 from include/linux/utsname.h:35,
                 from /warthog/am33/linux-2.6-mn10300/arch/mn10300/include/asm/elf.h:15,
                 from include/linux/elf.h:7,
                 from include/linux/module.h:14,
                 from init/main.c:13:
include/linux/sysfs.h:177: warning: parameter 1 ('type') has incomplete type
In file included from include/linux/kobject.h:21,
                 from include/linux/sched.h:91,
                 from arch/mn10300/mm/init.c:13:
include/linux/sysfs.h:177: warning: parameter 1 ('type') has incomplete type
In file included from include/linux/kobject.h:21,
                 from include/linux/sched.h:91,
                 from include/linux/utsname.h:35,
                 from /warthog/am33/linux-2.6-mn10300/arch/mn10300/include/asm/elf.h:15,
                 from include/linux/elf.h:7,
                 from include/linux/module.h:14,
                 from arch/mn10300/kernel/process.c:11:
include/linux/sysfs.h:177: warning: parameter 1 ('type') has incomplete type
...


The problem appears to be that 

	enum kobj_ns_type

is defined in linux/kobject.h but referenced in linux/sysfs.h, which is
included by linux/kobject.h.  Whilst I see a predeclaration at the top of
linux/sysfs.h, my compiler seems to ignore it.

The compiler is:

	gcc version 3.4-am33-04r2-5

which is a supported version according to the compiler-gcc3.h header file.

David

  reply	other threads:[~2010-08-12 11:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-11 14:01 [PATCH] Break the kobject namespace defs into their own header David Howells
2010-08-11 15:07 ` Greg KH
2010-08-12 11:56   ` David Howells [this message]
2010-08-12 17:02     ` 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=12812.1281614185@redhat.com \
    --to=dhowells@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=gregkh@suse.de \
    --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