From: Manish Lachwani <mlachwani@mvista.com>
To: linux-kernel@vger.kernel.org
Cc: akpm@osdl.org, mlachwani@mvista.com
Subject: [PATCH] Fix compile errors with 2.6.11-rc2
Date: Fri, 28 Jan 2005 13:34:00 -0800 [thread overview]
Message-ID: <20050128213400.GA20234@prometheus.mvista.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 882 bytes --]
Hi !
When compiling 2.6.11-rc2:
...
CC kernel/stop_machine.o
In file included from include/linux/sysdev.h:24,
from include/linux/cpu.h:22,
from include/linux/stop_machine.h:8,
from kernel/stop_machine.c:1:
include/linux/kobject.h: In function `to_kset':
include/linux/kobject.h:116: warning: implicit declaration of function `container_of'
include/linux/kobject.h:116: error: parse error before "struct"
include/linux/kobject.h:117: warning: no return statement in function returning non-void
include/linux/kobject.h: In function `subsys_get':
include/linux/kobject.h:224: error: parse error before "struct"
include/linux/kobject.h:225: warning: no return statement in function returning non-void
make[1]: *** [kernel/stop_machine.o] Error 1
make: *** [kernel] Error 2
Attached patch fixes this.
Thanks
Manish Lachwani
[-- Attachment #2: patch_kobject.patch --]
[-- Type: text/plain, Size: 450 bytes --]
Signed-off-by: Manish Lachwani <mlachwani@mvista.com>
Index: linux-2.6.11-rc2/include/linux/kobject.h
===================================================================
--- linux-2.6.11-rc2.orig/include/linux/kobject.h
+++ linux-2.6.11-rc2/include/linux/kobject.h
@@ -23,6 +23,7 @@
#include <linux/rwsem.h>
#include <linux/kref.h>
#include <linux/kobject_uevent.h>
+#include <linux/kernel.h>
#include <asm/atomic.h>
#define KOBJ_NAME_LEN 20
reply other threads:[~2005-01-28 21:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050128213400.GA20234@prometheus.mvista.com \
--to=mlachwani@mvista.com \
--cc=akpm@osdl.org \
--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
all inboxes | Powered by JetHome®