From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Paul Mackerras <paulus@linuxcare.com>
Cc: Andreas Tobler <toa@pop.agri.ch>,
Linux -Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: 2.3.39 compiles & boot
Date: Fri, 14 Jan 2000 02:05:09 -0500 [thread overview]
Message-ID: <387ECAA5.CBBCBC2C@mandrakesoft.com> (raw)
In-Reply-To: 00011313582505.00484@argo.linuxcare.com.au
Paul Mackerras wrote:
>
> On Thu, 13 Jan 2000, Andreas Tobler wrote:
>
> > may some of you are as far as I am, otherwise here is the diff I had to
> > do to get a 2.3.39-linus-tree to compile & boot with a Wallstreet I.
> > hope to ok otherwise let me please know.
>
> I think this patch is not quite the best way to do it. We already had
> 32-bit uids so we don't need the compatibility crap. Here is a patch that
> fixes the compile (alternatively my linux-pmac-devel rsync tree has a
> 2.3.39 tree that compiles and works).
Take a look at 2.3.40-pre2. It includes my uid16 fixes to the core and
to the Alpha arch. The Alpha didn't need the 16-bit compatibility mess
either.
CONFIG_UID16 is now the define to test... I simply added "define_bool
CONFIG_UID16 n" to arch/alpha/config.in, just to make it plain that the
compatibility stuff was not wanted.
Regards,
Jeff
--
Jeff Garzik | Demotivator of the month: MISTAKES
Building 1024 | It Could Be That The Purpose Of Your Life
MandrakeSoft, Inc. | Is Only To Serve As A Warning For Others.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-01-14 7:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-12 22:55 2.3.39 compiles & boot Andreas Tobler
2000-01-13 2:56 ` Paul Mackerras
2000-01-14 7:05 ` Jeff Garzik [this message]
2000-02-17 18:58 ` kernel powerbook sleep docs Brad Midgley
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=387ECAA5.CBBCBC2C@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@linuxcare.com \
--cc=toa@pop.agri.ch \
/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.