From: Ingo Molnar <mingo@elte.hu>
To: Jaswinder Singh Rajput <jaswinder@infradead.org>
Cc: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>,
Petr Titera <P.Titera@century.cz>,
linux-kernel@vger.kernel.org
Subject: Re: Build error on latest git
Date: Sun, 11 Jan 2009 14:51:22 +0100 [thread overview]
Message-ID: <20090111135122.GB18299@elte.hu> (raw)
In-Reply-To: <1231679335.3244.1.camel@jaswinder.satnam>
* Jaswinder Singh Rajput <jaswinder@infradead.org> wrote:
> On Sun, 2009-01-11 at 18:36 +0530, Jaswinder Singh Rajput wrote:
> > On Sun, Jan 11, 2009 at 5:27 PM, Petr Titera <P.Titera@century.cz> wrote:
> > > Going through source it seems to me (still building) that it is caused by
> > > including asm/smp.h only if build with CONFIG_SMP. This patch seems to fix
> > > this
> > >
> > > diff --git a/include/linux/smp.h b/include/linux/smp.h
> > > index b824669..fd51bb9 100644
> > > --- a/include/linux/smp.h
> > > +++ b/include/linux/smp.h
> > > @@ -11,6 +11,8 @@
> > > #include <linux/list.h>
> > > #include <linux/cpumask.h>
> > >
> > > +#include <asm/smp.h>
> > > +
> > > extern void cpu_idle(void);
> > >
> >
> > No, this is wrong.
> >
> > asm/smp.h should only be included when CONFIG_SMP is defined.
> >
> > I will send fix of this.
> >
>
> Here is the temporary fix, later on I will remove non-smp data from
> smp.h
>
> Subject: [PATCH] x86: mpparse.c fix compilation error
>
> Impact: fix compilation error
>
> Signed-off-by: Jaswinder Singh Rajput <jaswinderrajput@gmail.com>
> ---
> arch/x86/kernel/mpparse.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
applied to tip/x86/urgent, thanks Jaswinder!
Ingo
next prev parent reply other threads:[~2009-01-11 13:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 9:49 Build error on latest git Petr Titera
2009-01-11 11:57 ` Petr Titera
2009-01-11 13:06 ` Jaswinder Singh Rajput
2009-01-11 13:08 ` Jaswinder Singh Rajput
2009-01-11 13:51 ` Ingo Molnar [this message]
2009-01-11 14:54 ` Petr Titera
2009-01-11 15:04 ` Jaswinder Singh Rajput
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=20090111135122.GB18299@elte.hu \
--to=mingo@elte.hu \
--cc=P.Titera@century.cz \
--cc=jaswinder@infradead.org \
--cc=jaswinderlinux@gmail.com \
--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