From: Marc Wilson <mwilson@moonkingdom.net>
To: linux-kernel@vger.kernel.org
Subject: Re: No love for the PPC
Date: Fri, 12 Oct 2001 10:56:43 -0700 [thread overview]
Message-ID: <20011012105643.C30739@moonkingdom.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0110121002200.13818-100000@asuka.nerv-9.net>
In-Reply-To: <Pine.LNX.4.21.0110121002200.13818-100000@asuka.nerv-9.net>
On Fri, Oct 12, 2001 at 10:08:39AM -0700, Mike Borrelli wrote:
> 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?
An -ac kernel is SUPPOSED to break. It's not a release kernel. WHEN it
breaks, it gets fixed, and then it becomes a release kernel.
Seems simple enough.
If you want intermediate kernel revisions that don't break, head over to
http://penguinppc.org and look at how to rsync yourself a benh or bk
kernel tree.
--
Marc Wilson
mwilson@moonkingdom.net
mwilson@cts.com
next prev parent reply other threads:[~2001-10-12 17:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-12 17:08 No love for the PPC Mike Borrelli
2001-10-12 17:30 ` Larry McVoy
2001-10-13 0:01 ` Aaron Lehmann
2001-10-13 0:53 ` Mike Fedyk
2001-10-12 17:56 ` Marc Wilson [this message]
2001-10-12 20:43 ` John Alvord
2001-10-13 4:52 ` Albert D. Cahalan
2001-10-13 5:46 ` Benjamin Herrenschmidt
2001-10-13 12:24 ` Olaf Hering
2001-10-13 18:47 ` Mike Fedyk
2001-10-13 20:44 ` Tom Rini
2001-10-15 5:57 ` Geert Uytterhoeven
2001-10-13 7:46 ` Paul Mackerras
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=20011012105643.C30739@moonkingdom.net \
--to=mwilson@moonkingdom.net \
--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