From: Shaw Terwilliger <sterwill@io.nu>
To: Paul Mackerras <paulus@linuxcare.com>
Cc: Martin Costabel <costabel@wanadoo.fr>, linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.3.30-pre3
Date: Tue, 30 Nov 1999 14:39:01 -0600 [thread overview]
Message-ID: <19991130143901.A30660@io.nu> (raw)
In-Reply-To: <99120107124704.02316@argo.linuxcare.com.au>; from paulus@linuxcare.com on Wed, Dec 01, 1999 at 07:07:06AM +1100
Paul Mackerras wrote:
> This is (partly at least) my fault. I upgraded to 2.3.30-pre3 (a merge of
> my tree and Cort's), found it didn't work, and reverted the devel tree to
> 2.3.29, which does work just fine for me.
Well, I was just using the old rsync repository at samba.anu.edu.au, not
at linuxcare.com.au. However, the keyboard.h file had been that
way for a few weeks, probably unnoticed while everyone used the newer
repository. I did a little patching and that kernel's running fine
on my laptop.
I would ask that perhaps samba.anu.edu.au::linux-pmac-[stable/devel]
be turned off (or print a nice MOTD with the new location) since there
are countless web pages out there that still point to it.
> maybe I was updating it as he was fetching it or something. I have
> changed the ifdef in chipsfb.c as Shaw suggested.
It looked right to me, but I didn't have a chips device to test it with.
Just seemed like an unnecessary test and kept me (and presumably others)
from compiling it.
--
Shaw Terwilliger (sterwill@io.nu)
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-11-30 20:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-28 21:35 2.3.30-pre3 Geert Uytterhoeven
1999-11-28 21:49 ` 2.3.30-pre3 Shaw Terwilliger
1999-11-28 21:54 ` 2.3.30-pre3 Eric Benard
1999-11-28 23:06 ` 2.3.30-pre3 BenH
1999-11-29 4:17 ` 2.3.30-pre3 Shaw Terwilliger
1999-11-29 8:19 ` 2.3.30-pre3 Martin Costabel
1999-11-30 20:07 ` 2.3.30-pre3 Paul Mackerras
1999-11-30 20:39 ` Shaw Terwilliger [this message]
1999-11-30 20:44 ` 2.3.30-pre3 Ani Joshi
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=19991130143901.A30660@io.nu \
--to=sterwill@io.nu \
--cc=costabel@wanadoo.fr \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@linuxcare.com \
/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.