From: Peter Korsgaard <jacmet@sunsite.dk>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-embedded@ozlabs.org, Dan Malek <dan@embeddedalley.com>
Subject: Re: [RFC] arch/ppc/boot/simple/embed_boot.c : Merging all keyvals parsing code
Date: Tue, 31 Jan 2006 21:31:56 +0100 [thread overview]
Message-ID: <87slr4b0lf.fsf@48ers.dk> (raw)
In-Reply-To: <20060131142433.GN22672@smtp.west.cox.net> (Tom Rini's message of "Tue, 31 Jan 2006 07:24:34 -0700")
>>>>> "Tom" == Tom Rini <trini@kernel.crashing.org> writes:
Tom> I would suggest either Linus' current git tree or 2.6.16-rc1 if
Tom> you don't use git. But please bear in mind that since this is a
Tom> new feature (a new board) it won't be submitted to Linus' tree
Tom> until 2.6.17-rc1 opens up (and if in that time, it becomes much
Tom> easier to put this board under arch/powerpc it should be done
Tom> under there, instead).
I only recently moved from 2.4 to 2.6, so this may be a FAQ, but a
quick googling around didn't find anything.
What is this arch/ppc -> arch/powerpc about? Some kind of
consolidation of ppc and ppc64? What's the reason behind it and what
kind of time frame are we talking about? Is it related to the bd_t ->
flattened OF tree change?
Could someone post a few pointers to more information?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2006-01-31 20:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 11:15 [RFC] arch/ppc/boot/simple/embed_boot.c : Merging all keyvals parsing code Laurent Pinchart
2006-01-25 15:48 ` Dan Malek
2006-01-25 16:02 ` Laurent Pinchart
2006-01-30 17:28 ` Tom Rini
2006-01-31 8:47 ` Laurent Pinchart
2006-01-31 14:24 ` Tom Rini
2006-01-31 20:31 ` Peter Korsgaard [this message]
2006-01-31 20:40 ` Jon Loeliger
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=87slr4b0lf.fsf@48ers.dk \
--to=jacmet@sunsite.dk \
--cc=dan@embeddedalley.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=trini@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.