From: Dan Malek <dan@embeddededge.com>
To: Jaap-Jan Boor <jjboor@aimsys.nl>
Cc: Wolfgang Denk <wd@denx.de>, Tolunay Orkun <listmember@orkun.us>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: IBM 440GX, Ocotea...
Date: Tue, 23 Mar 2004 13:24:11 -0500 [thread overview]
Message-ID: <406080CB.5040403@embeddededge.com> (raw)
In-Reply-To: 1080061066.8019.70.camel@linpc003.aimsys.nl
Jaap-Jan Boor wrote:
> from what 'official ppc' tree do patches eventually get into the
> official linux kernel tree(s) at kernel.org?
> only linuxppc-2.4? Or all?
It seems to be a circuitous route that I don't even understand
anymore. Sometime stuff I check in gets there, sometimes not. :-)
http://penguinppc.org/dev/kernel.shtml tries to explain it.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-03-23 18:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 11:02 IBM 440GX, Ocotea Wolfgang Grandegger
2004-03-23 16:03 ` Tolunay Orkun
2004-03-23 16:44 ` Wolfgang Denk
2004-03-23 16:57 ` Jaap-Jan Boor
2004-03-23 17:38 ` Wolfgang Denk
2004-03-23 18:24 ` Dan Malek [this message]
2004-03-24 8:07 ` Jaap-Jan Boor
2004-03-24 22:25 ` Tom Rini
2004-03-25 7:57 ` Jaap-Jan Boor
2004-03-25 19:40 ` Tom Rini
2004-03-25 21:14 ` Tolunay Orkun
2004-03-25 21:20 ` Tom Rini
2004-03-25 21:23 ` Tolunay Orkun
2004-03-25 12:12 ` Paul Mackerras
2004-03-25 13:16 ` Jaap-Jan Boor
2004-03-23 18:31 ` Eugene Surovegin
2004-03-24 8:49 ` Wolfgang Grandegger
2004-03-24 8:59 ` IBM 440GX performance (was Re: IBM 440GX, Ocotea...) Wolfgang Grandegger
2004-03-24 12:24 ` USB problem on 2.4.20 song sam
[not found] ` <20040324234025.GA11675@gate.ebshome.net>
2004-03-25 8:02 ` IBM 440GX performance (was Re: IBM 440GX, Ocotea...) Gerhard Jaeger
2004-03-25 19:43 ` Eugene Surovegin
-- strict thread matches above, loose matches on Subject: below --
2004-03-24 14:21 IBM 440GX, Ocotea Neil Wilson
2004-03-24 16:05 ` Matt Porter
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=406080CB.5040403@embeddededge.com \
--to=dan@embeddededge.com \
--cc=jjboor@aimsys.nl \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=listmember@orkun.us \
--cc=wd@denx.de \
/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).