Re: Voyager phys_cpu_present_map compile error

[Adrian Bunk]

On Mon, Apr 21, 2008 at 10:29:19PM +0200, Ingo Molnar wrote:
> 
> * Adrian Bunk <bunk@xxxxxxxxxx> wrote:
> 
> > On Mon, Apr 21, 2008 at 10:13:52PM +0200, Ingo Molnar wrote:
> > > 
> > > * Adrian Bunk <bunk@xxxxxxxxxx> 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.

Your point is?

I'm compile testing 22 architectures (especially when sending my own 
patches), and whether a kernel would boot on my computer doesn't make 
any difference.

Why do you as an architecture maintainer want me to no longer spend my 
spare time on compile testing one of the subarchitectures of your 
architecture?

Other architecture maintainers tend to say "thanks for your bug report" 
and "thanks for your patch" when I'm sending bug reports and patches for 
platforms that have userbases comparable to Voyager...

> 	Ingo

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/