From: Tom Rini <trini@kernel.crashing.org>
To: Chris Clark <linuxppc-embedded@2nerds.com>
Cc: Wolfgang Denk <wd@denx.de>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Relationship between bk libuxppc-2.4 and denx linuxppc_2_4_devel
Date: Fri, 11 Jun 2004 14:44:17 -0700 [thread overview]
Message-ID: <20040611214417.GC925@smtp.west.cox.net> (raw)
In-Reply-To: <Pine.GSO.4.53.0406111437580.9184@solaris.xmission.com>
On Fri, Jun 11, 2004 at 02:59:48PM -0600, Chris Clark wrote:
>
> On Fri, 11 Jun 2004, Wolfgang Denk wrote:
> > You should work with the official trees, i. e. linuxppc-2.4 or
> > linuxppc-2.5.
>
> Unless I made some mistake in cloning the linuxppc-2.{4,5} trees from
> ppc.bkbits.net, (which is entirely possible as I'm a BK newbie), there
> appears to be a fair amount of processor- and platform-specific stuff
> in the Denx linuxppc_2_4_devel CVS tree which does not appear in the
> ppc.bkbits.net BK trees (e.g. arch/ppc/5xxx_io/... ).
>
> Is the Denx CVS tree "authoritative" with regard to those extras? Is
> there any expectation that those bits found only in the Denx CVS tree
> will eventually find their way into the ppc.bkbits.net tree(s)? (Or
> some other, more appropriate tree(s)? If so, which?)
For 2.4? Denx will probably be the "authoritative" tree. For 2.6 I am
hopeful that something can be worked out.
--
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-06-11 21:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-10 23:53 Relationship between bk libuxppc-2.4 and denx linuxppc_2_4_devel Stephen Williams
2004-06-11 7:30 ` Wolfgang Denk
2004-06-11 20:59 ` Chris Clark
2004-06-11 21:44 ` Tom Rini [this message]
2004-06-11 21:58 ` Wolfgang Denk
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=20040611214417.GC925@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=linuxppc-embedded@2nerds.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--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).