From: "Allen Curtis" <acurtis@onz.com>
To: "Armin" <akuster@pacbell.net>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: RE: Stable BK for 405GP Walnut?
Date: Wed, 22 May 2002 19:21:09 -0700 [thread overview]
Message-ID: <NCBBIINEHIPFGJPLBEIFKEHMDHAA.acurtis@onz.com> (raw)
In-Reply-To: <3CEBD3A2.8090200@pacbell.net>
>you will find all that in linuxppc_2_4_devel
Are you saying that the code will not make it into stable? Are you saying
that stable does not compile for the Walnut? What is your recommendation?
Take the stable or kernel.org 2.4.18 w/PPC patch and then all the "devel"
pieces that are missing?
TIA
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-05-23 2:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-22 4:35 Stable BK for 405GP Walnut? Allen Curtis
2002-05-22 17:21 ` Armin
2002-05-23 2:21 ` Allen Curtis [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=NCBBIINEHIPFGJPLBEIFKEHMDHAA.acurtis@onz.com \
--to=acurtis@onz.com \
--cc=akuster@pacbell.net \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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).