From: Paul Mackerras <paulus@linuxcare.com>
To: Martin Costabel <costabel@wanadoo.fr>, Shaw Terwilliger <sterwill@io.nu>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.3.30-pre3
Date: Wed, 1 Dec 1999 07:07:06 +1100 [thread overview]
Message-ID: <99120107124704.02316@argo.linuxcare.com.au> (raw)
In-Reply-To: 38423714.D5136535@wanadoo.fr
On Mon, 29 Nov 1999, Martin Costabel wrote:
> Are there several different versions of Paul's devel tree? The one I am
> getting is only at version 2.3.29 and has been nicely compiling and
> running for me for a while now. I don't know about chipsfb.c which I am
> not using, but the others of your patches are essentially those that A.
> Joshi has published a long time ago. And they don't apply to my version
> of Paul's devel tree, because they are already built in.
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.
I think that Shaw possibly got a corrupted include/asm-ppc/keyboard.h,
maybe I was updating it as he was fetching it or something. I have
changed the ifdef in chipsfb.c as Shaw suggested.
Paul.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-11-30 20:07 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 ` Paul Mackerras [this message]
1999-11-30 20:39 ` 2.3.30-pre3 Shaw Terwilliger
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=99120107124704.02316@argo.linuxcare.com.au \
--to=paulus@linuxcare.com \
--cc=costabel@wanadoo.fr \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=sterwill@io.nu \
/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;
as well as URLs for NNTP newsgroup(s).