From: Ingo Molnar <mingo@elte.hu>
To: Adrian Bunk <bunk@kernel.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Alexey Starikovskiy <astarikovskiy@suse.de>,
tglx@linutronix.de, hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: Voyager phys_cpu_present_map compile error
Date: Mon, 21 Apr 2008 22:29:19 +0200 [thread overview]
Message-ID: <20080421202919.GA28069@elte.hu> (raw)
In-Reply-To: <20080421202605.GC2633@cs181133002.pp.htv.fi>
* Adrian Bunk <bunk@kernel.org> wrote:
> On Mon, Apr 21, 2008 at 10:13:52PM +0200, Ingo Molnar wrote:
> >
> > * Adrian Bunk <bunk@kernel.org> wrote:
> >
> > > > ok, that's good enough - that's why i excluded it from the auto-qa
> > > > test-space as well. Adrian, could you please remove it from your
> > > > config testset as well? If a user enables that config option it wont
> > > > boot anyway so it's not a problem in practice.
> > >
> > > Who said that Voyager won't boot?
> >
> > Adrian, you build Voyager kernels so just try to boot it once on
> > your PC and watch the show ...
>
> Ingo, an ia64 kernel also won't boot on my computer, and I'll still
> compile test my patches for ia64 ...
dont be silly... the ia64 kernel is not under arch/x86, it's not even
the same instruction format. Voyager runs on x86 CPUs and is part of the
x86 architecture tree.
Ingo
next prev parent reply other threads:[~2008-04-21 20:29 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 0:02 Voyager phys_cpu_present_map compile error Adrian Bunk
2008-04-21 8:53 ` Adrian Bunk
2008-04-21 12:00 ` Ingo Molnar
2008-04-21 12:55 ` H. Peter Anvin
2008-04-21 14:10 ` Status of SGI 320/540 (Visual Workstation) support? Adrian Bunk
2008-04-22 6:19 ` Andrey Panin
2008-04-22 13:29 ` Voyager phys_cpu_present_map compile error Andrew Morton
2008-04-22 15:25 ` Andy Whitcroft
2008-04-21 13:00 ` H. Peter Anvin
2008-04-21 15:42 ` James Bottomley
2008-04-21 20:03 ` Ingo Molnar
2008-04-21 23:08 ` James Bottomley
2008-04-21 19:55 ` Ingo Molnar
2008-04-21 20:03 ` H. Peter Anvin
2008-04-21 20:11 ` Ingo Molnar
2008-04-21 20:10 ` H. Peter Anvin
2008-04-23 8:53 ` Pavel Machek
2008-04-21 13:27 ` Adrian Bunk
2008-04-21 20:14 ` Ingo Molnar
2008-04-21 21:57 ` James Bottomley
2008-04-25 14:50 ` James Bottomley
2008-04-25 16:17 ` Adrian Bunk
2008-04-25 16:33 ` James Bottomley
2008-04-28 17:59 ` Ingo Molnar
2008-04-28 19:09 ` James Bottomley
2008-04-21 15:58 ` James Bottomley
2008-04-21 19:51 ` Ingo Molnar
2008-04-21 20:09 ` Adrian Bunk
2008-04-21 20:13 ` Ingo Molnar
2008-04-21 20:26 ` Adrian Bunk
2008-04-21 20:29 ` Ingo Molnar [this message]
2008-04-21 21:02 ` Adrian Bunk
2008-04-21 22:31 ` Ingo Molnar
2008-04-26 7:43 ` Pavel Machek
2008-04-27 0:44 ` H. Peter Anvin
2008-04-27 1:06 ` Adrian Bunk
2008-04-27 1:45 ` H. Peter Anvin
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=20080421202919.GA28069@elte.hu \
--to=mingo@elte.hu \
--cc=James.Bottomley@HansenPartnership.com \
--cc=astarikovskiy@suse.de \
--cc=bunk@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.