From: keith mannthey <kmannth@us.ibm.com>
To: Jiri Kosina <jikos@jikos.cz>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] make mach-generic/summit.c compile on UP
Date: Thu, 05 Oct 2006 15:24:53 -0700 [thread overview]
Message-ID: <1160087093.5664.14.camel@keithlap> (raw)
In-Reply-To: <Pine.LNX.4.64.0610052308000.12556@twin.jikos.cz>
On Thu, 2006-10-05 at 23:18 +0200, Jiri Kosina wrote:
> On Thu, 5 Oct 2006, keith mannthey wrote:
>
> > > In file included from arch/i386/mach-generic/summit.c:17:
> > > include/asm/mach-summit/mach_apic.h: In function 'apicid_to_node':
> > > include/asm/mach-summit/mach_apic.h:91: error: 'apicid_2_node' undeclared (first use in this function)
> > > include/asm/mach-summit/mach_apic.h:91: error: (Each undeclared identifier is reported only once
> > > include/asm/mach-summit/mach_apic.h:91: error: for each function it appears in.)
> > > Is the patch below correct?
> > Well I guess it would fix the apicid_2_node build error but I can't
> > think of a single good reason to be in a config where you would need any
> > of the summit code in UP. Perhaps a kconfig or makefile change in the
> > right spot would be better.
>
> Yes, this was in fact a product of a random .config (but allowed by
> Kconfig rules). There should definitely be a Kconfig rule not allowing
> having this non-working .config settings.
>
> I guess that probably making CONFIG_X86_GENERIC dependent on CONFIG_SMP
> would not be good, because the mach-default/ makes sense even on UP, am I
> right
Yea I am pretty sure CONFIG_X86_GENERIC is ment to boot UP and SMP
kernels.
Maybe just moving apicid_2_node to a UP safe location would be a good
way to go as well. I overlooked the fact that CONFIG_X86_GENERIC wasn't
always SMP.
Thanks,
Keith
next prev parent reply other threads:[~2006-10-05 22:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 17:16 [PATCH] make mach-generic/summit.c compile on UP Jiri Kosina
2006-10-05 20:31 ` keith mannthey
2006-10-05 21:18 ` Jiri Kosina
2006-10-05 22:24 ` keith mannthey [this message]
2006-10-06 9:11 ` Jiri Kosina
2006-10-06 17:23 ` keith mannthey
2006-10-05 23:11 ` Andi Kleen
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=1160087093.5664.14.camel@keithlap \
--to=kmannth@us.ibm.com \
--cc=jikos@jikos.cz \
--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