From: Ingo Molnar <mingo@elte.hu>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Yinghai Lu <yhlu.kernel@gmail.com>
Subject: Re: [PATCH] fix compile breakage casued by x86: move prefill_possible_map calling early
Date: Thu, 30 Oct 2008 22:56:52 +0100 [thread overview]
Message-ID: <20081030215652.GH30303@elte.hu> (raw)
In-Reply-To: <1225402115.19324.40.camel@localhost.localdomain>
* James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> >From 2947cdda39c36e5a0d56fe0c6b70a17526abb5b5 Mon Sep 17 00:00:00 2001
> From: James Bottomley <James.Bottomley@HansenPartnership.com>
> Date: Thu, 30 Oct 2008 15:51:22 -0500
> Subject: [VOYAGER] add prefill_possible_mask() to fix linker breakage
>
> Before
>
> commit 329513a35d1a2b6b28d54f5c2c0dde4face8200b
> Author: Yinghai Lu <yhlu.kernel@gmail.com>
> Date: Wed Jul 2 18:54:40 2008 -0700
>
> x86: move prefill_possible_map calling early
>
> prefill_possible_mask() was hidden under CONFIG_HOTPLUG_CPU rendering
> it invisitble to voyager. Since this commit it's exposed, but not
> provided by the voyager subarch, so add a dummy stub to fix the link
> breakage.
>
> Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
> ---
> arch/x86/mach-voyager/voyager_smp.c | 6 ++++++
> 1 files changed, 6 insertions(+), 0 deletions(-)
applied to tip/x86/urgent, thanks James!
these kinds of problems will go away too when x86/Voyager becomes part
of the regular platform code.
Ingo
prev parent reply other threads:[~2008-10-30 21:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 21:28 James Bottomley
2008-10-30 21:56 ` Ingo Molnar [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=20081030215652.GH30303@elte.hu \
--to=mingo@elte.hu \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yhlu.kernel@gmail.com \
/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®