mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Mike Borrelli <mike@nerv-9.net>
Cc: linux-kernel@vger.kernel.org, alan@redhat.com
Subject: Re: No love for the PPC
Date: Sat, 13 Oct 2001 17:46:05 +1000 (EST)	[thread overview]
Message-ID: <15303.61757.56505.363551@cargo.ozlabs.ibm.com> (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>

Mike Borrelli writes:

> 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).

I'm afraid I am to blame for this one.  It looks like we sent Alan a
patch which isn't appropriate for Alan's tree (because Alan's and
Linus' trees VM system is different).  Here is a patch to reverse the
breakage.

> Anyway, the real question is, why does the ppc arhitecture /always/ break
> between versions?

Well, the port maintainers don't get any earlier access to the
releases than everyone else.  So if some change breaks the compile for
PPC (or any other architecture), we just have to send a patch to Linus
or Alan and hope that it gets accepted for the next release (when
there could easily be another change that breaks things in some other
way, of course).  That said, Alan is usually very good about accepting
our patches in a timely fashion, and as I said, the process.c breakage
is our fault not his.

With Linus' trees, it would be nice if there were some restrictions on
what sort of changes can go in between the last prerelease and the
final release - if it was restricted to changes under arch/ and
include/asm-*, obvious compile fixes, or really critical bug fixes,
then there would be a better chance that the final release would work
for most architectures.  But that does not seem to be a priority at
this stage.

Paul.

diff -urN ac2412-1/arch/ppc/kernel/process.c acppc/arch/ppc/kernel/process.c
--- ac2412-1/arch/ppc/kernel/process.c	Wed Oct 10 12:38:52 2001
+++ acppc/arch/ppc/kernel/process.c	Sat Oct 13 16:50:32 2001
@@ -48,6 +48,7 @@
 
 struct task_struct *last_task_used_math = NULL;
 struct task_struct *last_task_used_altivec = NULL;
+static struct vm_area_struct init_mmap = INIT_MMAP;
 static struct fs_struct init_fs = INIT_FS;
 static struct files_struct init_files = INIT_FILES;
 static struct signal_struct init_signals = INIT_SIGNALS;

      parent reply	other threads:[~2001-10-13  7:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-12 17:08 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
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 [this message]

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=15303.61757.56505.363551@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=alan@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike@nerv-9.net \
    /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

all inboxes | Powered by JetHome®