From: Brian Uhrain <buhrain@rosettastone.com>
To: Tomi Lapinlampi <lapinlam@vega.lnet.lut.fi>
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org
Subject: Re: 2.6.16.6 ( - 2.6.16.11 ) compile failure on an alpha
Date: Tue, 25 Apr 2006 11:29:25 +0100 [thread overview]
Message-ID: <444DFA05.2060508@rosettastone.com> (raw)
In-Reply-To: <20060425101647.GH4349@vega.lnet.lut.fi>
[-- Attachment #1: Type: text/plain, Size: 609 bytes --]
Hi,
Tomi Lapinlampi wrote:
> When trying to compile 2.6.16.11 on an alpha I encountered a compile
> error in arch/alpha/kernel/setup.c. I found that the problem appears with
> all kernels from 2.6.16.6 up to 2.6.16.11.
> 2.6.16.5 compiles fine, just like all older 2.6.16 -releases.
> I did not test this with 2.6.17-rc -kernels.
The problem is that the version of the patch meant for the 2.6.17-rc
kernels was merged into 2.6.16.5. 'for_each_possible_cpu' does not
exist in the 2.6.16.x tree. Attached is a patch that replaces the usage
of for_each_possible_cpu with the 2.6.16 equivalent.
- Brian
[-- Attachment #2: 2.6.16.11-alpha-compile-fix.patch --]
[-- Type: text/plain, Size: 723 bytes --]
Signed-off-by: Brian Uhrain <buhrain@rosettastone.com>
---
arch/alpha/kernel/setup.c | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
--- linux-2.6.16.11.orig/arch/alpha/kernel/setup.c 2006-04-25 11:21:03.000000000 +0100
+++ linux-2.6.16.11/arch/alpha/kernel/setup.c 2006-04-25 11:22:56.557266608 +0100
@@ -483,11 +483,13 @@ register_cpus(void)
{
int i;
- for_each_possible_cpu(i) {
- struct cpu *p = kzalloc(sizeof(*p), GFP_KERNEL);
- if (!p)
- return -ENOMEM;
- register_cpu(p, i, NULL);
+ for (i = 0; i < NR_CPUS; i++) {
+ if (cpu_possible(i)) {
+ struct cpu *p = kzalloc(sizeof(*p), GFP_KERNEL);
+ if (!p)
+ return -ENOMEM;
+ register_cpu(p, i, NULL);
+ }
}
return 0;
}
next prev parent reply other threads:[~2006-04-25 10:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-25 10:16 2.6.16.6 ( - 2.6.16.11 ) compile failure on an alpha Tomi Lapinlampi
2006-04-25 10:29 ` Brian Uhrain [this message]
2006-04-25 18:53 ` Jan-Benedict Glaw
2006-04-25 19:44 ` Greg KH
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=444DFA05.2060508@rosettastone.com \
--to=buhrain@rosettastone.com \
--cc=gregkh@suse.de \
--cc=lapinlam@vega.lnet.lut.fi \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.