> I'm sorry about the tone of this e-mail, but it is somewhat painful when,
> after downloading a new kernel to play with, it doesn't compile on the
> ppc. It isn't even big problems either. A single line (#include
> <linux/pm.h>) is missing from pc_keyb.c and has been for at least three
> -ac releases. Now, process.c in arch/ppc/kernel/ dies from an undeclared
> identifier (init_mmap).
...
> Anyway, the real question is, why does the ppc arhitecture /always/ break
> between versions?
At the most recent Ottata Linux Symposium, there was a PowerPC
session with about 20 people. Somebody did a poll, asking what
people used. I was the only person who dared to use a kernel
from Linus. Everone else was using the BenH and BitKeeper ones.
This is a sorry state of affairs. If people are off using kernels
from other places, there isn't a great incentive to keep the
official Linus kernel updated. Nobody uses it anyway.
Elimination of these non-Linus PowerPC trees would be great.
(at least the "stable" ones should go, as they lure people
away from the one true source tree)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/