From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Yinghai Lu <yinghai@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: fix missing cpu_index initialisation
Date: Thu, 30 Oct 2008 16:27:13 -0500 [thread overview]
Message-ID: <1225402033.19324.38.camel@localhost.localdomain> (raw)
In-Reply-To: <20081030212359.GC30303@elte.hu>
On Thu, 2008-10-30 at 22:23 +0100, Ingo Molnar wrote:
> * Yinghai Lu <yinghai@kernel.org> wrote:
>
> > CC arch/x86/kernel/cpu/common.o
> > arch/x86/kernel/cpu/common.c: In function 'early_identify_cpu':
> > arch/x86/kernel/cpu/common.c:553: error: 'boot_cpu_id' undeclared
> > (first use in this function)
> > arch/x86/kernel/cpu/common.c:553: error: (Each undeclared identifier
> > is reported only once
> > arch/x86/kernel/cpu/common.c:553: error: for each function it appears in.)
> > make[2]: *** [arch/x86/kernel/cpu/common.o] Error 1
> > make[1]: *** [arch/x86/kernel/cpu] Error 2
> > make: *** [arch/x86/kernel] Error 2
>
> depends on this patch perhaps:
>
> Subject: [PATCH] fix compile breakage caused by dc1e35c6e95e8923cf1d3510438b63c600fee1e2
Yes, sorry, that's what the line:
> Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
> ---
>
> Depends on [VOYAGER] x86: add ability to test for boot CPU
>
> arch/x86/kernel/cpu/common.c | 2 ++
Was supposed to convey
James
next prev parent reply other threads:[~2008-10-30 21:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 21:13 [PATCH] x86: fix missing cpu_index initialisation James Bottomley
2008-10-30 21:21 ` Yinghai Lu
2008-10-30 21:23 ` Ingo Molnar
2008-10-30 21:27 ` James Bottomley [this message]
2008-10-30 23:17 ` Ingo Molnar
2008-10-30 23:45 ` Ingo Molnar
2008-10-31 8:44 ` Ingo Molnar
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=1225402033.19324.38.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yinghai@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