public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Brice Goglin <Brice.Goglin@ens-lyon.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-rc3-mm1
Date: Wed, 15 Feb 2006 10:26:40 +1100	[thread overview]
Message-ID: <200602151026.40852.kernel@kolivas.org> (raw)
In-Reply-To: <20060214122825.5b8de370.akpm@osdl.org>

On Wednesday 15 February 2006 07:28, Andrew Morton wrote:
> Brice Goglin <Brice.Goglin@ens-lyon.org> wrote:
> > Andrew Morton wrote:
> > >ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16-rc3
> > >/2.6.16-rc3-mm1/
> >
> > Hi Andrew,
> >
> > WARNING: speedstep-centrino.ko needs unknown symbol cpu_online_map
> >
> > This symbol is in include/linux/cpumask.h but actually only defined and
> > exported in smpboot.c which is not compiled on UP.
>
> diff -puN
> arch/i386/kernel/cpu/cpufreq/speedstep-centrino.c~git-acpi-up-fix-2
> arch/i386/kernel/cpu/cpufreq/speedstep-centrino.c ---
> devel/arch/i386/kernel/cpu/cpufreq/speedstep-centrino.c~git-acpi-up-fix-2	2
>006-02-14 12:27:41.000000000 -0800 +++
> devel-akpm/arch/i386/kernel/cpu/cpufreq/speedstep-centrino.c	2006-02-14
> 12:27:41.000000000 -0800 @@ -654,8 +654,10 @@ static int centrino_target
> (struct cpufr
>  		return -EINVAL;
>  	}
>
> +#ifdef CONFIG_SMP
>  	/* cpufreq holds the hotplug lock, so we are safe from here on */
>  	cpus_and(online_policy_cpus, cpu_online_map, policy->cpus);
> +#endif

Shouldn't the cpu_online_map be hardcoded to the first/only cpu on UP instead?

Cheers,
Con

  reply	other threads:[~2006-02-14 23:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-14  9:41 2.6.16-rc3-mm1 Andrew Morton
2006-02-14 11:07 ` 2.6.16-rc3-mm1 Marc Koschewski
2006-02-14 11:16 ` 2.6.16-rc3-mm1 Michal Piotrowski
2006-02-14 12:16   ` 2.6.16-rc3-mm1 Sander
2006-02-14 12:46     ` 2.6.16-rc3-mm1 Michal Piotrowski
2006-02-14 13:17 ` 2.6.16-rc3-mm1: i386 compilation broken Adrian Bunk
2006-02-14 13:27   ` Andi Kleen
2006-02-14 13:54     ` Michal Piotrowski
2006-02-14 20:23       ` Andrew Morton
2006-02-14 21:05         ` Andi Kleen
2006-02-14 21:08     ` Adrian Bunk
2006-02-15 13:19     ` Roman Zippel
2006-02-15 13:32       ` Andi Kleen
2006-02-14 14:00 ` 2.6.16-rc3-mm1: ISDN_DRV_GIGASET driver Adrian Bunk
2006-02-15  1:57   ` Tilman Schmidt
2006-02-15 22:10     ` Adrian Bunk
2006-02-14 14:33 ` 2.6.16-rc3-mm1 Brice Goglin
2006-02-14 20:28   ` 2.6.16-rc3-mm1 Andrew Morton
2006-02-14 23:26     ` Con Kolivas [this message]
2006-02-14 23:38       ` 2.6.16-rc3-mm1 Brice Goglin
2006-02-15  2:58       ` 2.6.16-rc3-mm1 Andrew Morton
2006-02-14 15:22 ` [-mm patch] block/blktrace.c: make blk_trace_cleanup() static Adrian Bunk
2006-02-14 15:23   ` Jens Axboe
2006-02-16 23:28 ` 2.6.16-rc3-mm1 Pavel Machek

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=200602151026.40852.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=Brice.Goglin@ens-lyon.org \
    --cc=akpm@osdl.org \
    --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