From: Martin Costabel <costabel@wanadoo.fr>
To: Shaw Terwilliger <sterwill@io.nu>
Cc: paulus@linuxcare.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.3.30-pre3
Date: Mon, 29 Nov 1999 09:19:32 +0100 [thread overview]
Message-ID: <38423714.D5136535@wanadoo.fr> (raw)
In-Reply-To: 19991128221713.A17532@io.nu
Shaw Terwilliger wrote:
>
> BenH wrote:
> > Yes, please, send me your patches. Paul will be away for a few weeks and
> > I want to move all my patches (there are more coming ;) to 2.3.x asap.
>
> OK... here they are. They're against paul's devel tree as of an hour
> ago. I'm running a fresh-built kernel from a tree with these applied;
> everything's working well.
>
> Besides being attached here, the individual patches (and the README) are
> available at http://www.abisource.com/~sterwill/patches/.
>
> If anyone else is interested in bulding the kernel, just grab the
> devel tree and do "patch -p0 < all.patch" from /usr/src (assuming
> the tree is /usr/src/linux).
<???>
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.
</???>
--
Martin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-11-29 8:19 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 ` Martin Costabel [this message]
1999-11-30 20:07 ` 2.3.30-pre3 Paul Mackerras
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=38423714.D5136535@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@linuxcare.com \
--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).