From: Tom Rini <trini@kernel.crashing.org>
To: Jaap-Jan Boor <jjboor@aimsys.nl>
Cc: Dan Malek <dan@embeddededge.com>,
linuxppc-embedded@lists.linuxppc.org,
Tolunay Orkun <listmember@orkun.us>, Wolfgang Denk <wd@denx.de>
Subject: Re: IBM 440GX, Ocotea...
Date: Wed, 24 Mar 2004 15:25:12 -0700 [thread overview]
Message-ID: <20040324222512.GM7126@smtp.west.cox.net> (raw)
In-Reply-To: <4B2752C7-7D6A-11D8-BC79-000A95B15278@aimsys.nl>
On Wed, Mar 24, 2004 at 09:07:28AM +0100, Jaap-Jan Boor wrote:
> On Mar 23, 2004, at 19:24, Dan Malek wrote:
>
> >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. :-)
>
> and you have never found out the conditions when something
> get's in (only when submitted at friday the 13th or something?)
Um, yeah. I'm hoping 2.6 will be different from 2.4 in that regard. :)
> >http://penguinppc.org/dev/kernel.shtml tries to explain it.
>
>
> this states you should build/submit patches against kernel.org's
> trees, which is quite different from linuxppc-2.[45], which is probably
> Tom Rini's checkout of kernel.org's tree with all ppc patches.
> Or is it?
linuxppc-2.[45] are children of the linux-2.[45] trees, and contain
stuff that's not quite ready to go out, _but_will_be_soon_ or has been
put in a tree for Linus/Marcelo, but they haven't pulled yet.
--
Tom Rini
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-03-24 22:25 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
2004-03-24 8:07 ` Jaap-Jan Boor
2004-03-24 22:25 ` Tom Rini [this message]
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=20040324222512.GM7126@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=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).