From: Peter Zijlstra <peterz@infradead.org>
To: Darren Hart <dvhart@linux.intel.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
"Ashfield, Bruce" <Bruce.Ashfield@windriver.com>
Subject: Re: [PATCH][RT] fix KM_TYPE_NR undeclared in sched.h on 32 bit x86
Date: Tue, 09 Aug 2011 10:31:29 +0200 [thread overview]
Message-ID: <1312878690.22367.48.camel@twins> (raw)
In-Reply-To: <4E40B2BF.3030608@linux.intel.com>
On Mon, 2011-08-08 at 21:08 -0700, Darren Hart wrote:
> 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>
Yep indeed, I wonder why my i386-defconfig build.. header deps magic or
so.
I've updated the patch in question, thanks!
prev parent reply other threads:[~2011-08-09 8:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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=1312878690.22367.48.camel@twins \
--to=peterz@infradead.org \
--cc=Bruce.Ashfield@windriver.com \
--cc=dvhart@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@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