All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	"Ashfield, Bruce" <Bruce.Ashfield@windriver.com>
Subject: [PATCH][RT] fix KM_TYPE_NR undeclared in sched.h on 32 bit x86
Date: Mon, 08 Aug 2011 21:08:31 -0700	[thread overview]
Message-ID: <4E40B2BF.3030608@linux.intel.com> (raw)

Patch peter_zijlstra-re-_3_0-rt4.patch causes 32 bit compilations to fail with:
sched.h:1592:17: error: ‘KM_TYPE_NR’ undeclared here (not in a function)

Including asm/kmap_types in sched.h resolves the issue.

Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Peter Zijlstra <peterz@infradead.org>
CC: Bruce Ashfield <bruce.ashfield@windriver.com>
---
 include/linux/sched.h |    1 +
 1 file changed, 1 insertion(+)

Index: linux-3.0-rt/include/linux/sched.h
===================================================================
--- linux-3.0-rt.orig/include/linux/sched.h
+++ linux-3.0-rt/include/linux/sched.h
@@ -63,6 +63,7 @@ struct sched_param {
 #include <linux/nodemask.h>
 #include <linux/mm_types.h>
 
+#include <asm/kmap_types.h>
 #include <asm/system.h>
 #include <asm/page.h>
 #include <asm/ptrace.h>
-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Darren Hart <dvhart@linux.intel.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	"Ashfield, Bruce" <Bruce.Ashfield@windriver.com>
Subject: [PATCH][RT] fix KM_TYPE_NR undeclared in sched.h on 32 bit x86
Date: Mon, 08 Aug 2011 21:08:31 -0700	[thread overview]
Message-ID: <4E40B2BF.3030608@linux.intel.com> (raw)

Patch peter_zijlstra-re-_3_0-rt4.patch causes 32 bit compilations to fail with:
sched.h:1592:17: error: ‘KM_TYPE_NR’ undeclared here (not in a function)

Including asm/kmap_types in sched.h resolves the issue.

Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Peter Zijlstra <peterz@infradead.org>
CC: Bruce Ashfield <bruce.ashfield@windriver.com>
---
 include/linux/sched.h |    1 +
 1 file changed, 1 insertion(+)

Index: linux-3.0-rt/include/linux/sched.h
===================================================================
--- linux-3.0-rt.orig/include/linux/sched.h
+++ linux-3.0-rt/include/linux/sched.h
@@ -63,6 +63,7 @@ struct sched_param {
 #include <linux/nodemask.h>
 #include <linux/mm_types.h>
 
+#include <asm/kmap_types.h>
 #include <asm/system.h>
 #include <asm/page.h>
 #include <asm/ptrace.h>
-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel

             reply	other threads:[~2011-08-09  4:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-09  4:08 Darren Hart [this message]
2011-08-09  4:08 ` [PATCH][RT] fix KM_TYPE_NR undeclared in sched.h on 32 bit x86 Darren Hart
2011-08-09  8:31 ` Peter Zijlstra
2011-08-09  8:31   ` Peter Zijlstra

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=4E40B2BF.3030608@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=Bruce.Ashfield@windriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=peterz@infradead.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 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.