mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: WANG Cong <xiyou.wangcong@gmail.com>
Cc: toralf.foerster@gmx.de, James.Bottomley@hansenpartnership.com,
	linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Mike Travis <travis@sgi.com>
Subject: Re: build issue #380 for v2.6.26-rc1-279-g28a4acb : mach-voyager: multiple definition of `phys_cpu_present_map'
Date: Fri, 9 May 2008 11:58:37 +0200	[thread overview]
Message-ID: <20080509095837.GB19617@elte.hu> (raw)
In-Reply-To: <20080509095244.GJ2543@hacking>


* WANG Cong <xiyou.wangcong@gmail.com> wrote:

> Sorry. Ignore previous one. This one should be correct, I think.
> 
> ---
> 
> diff --git a/arch/x86/mach-voyager/voyager_smp.c b/arch/x86/mach-voyager/voyager_smp.c
> index 8acbf0c..2e8388b 100644
> --- a/arch/x86/mach-voyager/voyager_smp.c
> +++ b/arch/x86/mach-voyager/voyager_smp.c
> @@ -74,7 +74,7 @@ EXPORT_SYMBOL(cpu_online_map);
>  
>  /* Bitmask of CPUs present in the system - exported by i386_syms.c, used
>   * by scheduler but indexed physically */
> -cpumask_t phys_cpu_present_map = CPU_MASK_NONE;
> +static cpumask_t phys_cpu_present_map = CPU_MASK_NONE;

i've got the one below queued up but it's stalled as it could easily be 
wrong and there's no ack from James yet and there's been discussion back 
and forth. James, what do you suggest?

	Ingo

-------------------->
Subject: x86, voyager: build fix
From: Ingo Molnar <mingo@elte.hu>
Date: Sun May 04 23:56:30 CEST 2008

Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
 arch/x86/mach-voyager/voyager_smp.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Index: linux-x86.q/arch/x86/mach-voyager/voyager_smp.c
===================================================================
--- linux-x86.q.orig/arch/x86/mach-voyager/voyager_smp.c
+++ linux-x86.q/arch/x86/mach-voyager/voyager_smp.c
@@ -74,7 +74,7 @@ EXPORT_SYMBOL(cpu_online_map);
 
 /* Bitmask of CPUs present in the system - exported by i386_syms.c, used
  * by scheduler but indexed physically */
-cpumask_t phys_cpu_present_map = CPU_MASK_NONE;
+extern cpumask_t phys_cpu_present_map;
 
 /* The internal functions */
 static void send_CPI(__u32 cpuset, __u8 cpi);

  reply	other threads:[~2008-05-09  9:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-09  9:13 Toralf Förster
2008-05-09  9:30 ` WANG Cong
2008-05-09  9:58   ` Toralf Förster
2008-05-09 10:16     ` WANG Cong
2008-05-09  9:52 ` WANG Cong
2008-05-09  9:58   ` Ingo Molnar [this message]
2008-05-09 10:09     ` WANG Cong
2008-05-09 10:59     ` Toralf Förster
2008-05-09 11:22       ` WANG Cong
2008-05-09 14:22     ` James Bottomley
2008-05-09 14:47       ` Ingo Molnar
2008-05-09 15:01         ` Alexey Starikovskiy
2008-05-10 13:17         ` Ingo Molnar
2008-05-10 14:01           ` James Bottomley
2008-05-10 14:21             ` James Bottomley
2008-05-10 14:34             ` WANG Cong

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=20080509095837.GB19617@elte.hu \
    --to=mingo@elte.hu \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=toralf.foerster@gmx.de \
    --cc=travis@sgi.com \
    --cc=xiyou.wangcong@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®