linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Laurent Pinchart <laurent.pinchart@tbox.biz>
Cc: Dan Malek <dan@embeddedalley.com>, linuxppc-embedded@ozlabs.org
Subject: Re: [RFC] arch/ppc/boot/simple/embed_boot.c : Merging all keyvals parsing code
Date: Tue, 31 Jan 2006 07:24:34 -0700	[thread overview]
Message-ID: <20060131142433.GN22672@smtp.west.cox.net> (raw)
In-Reply-To: <200601310947.32463.laurent.pinchart@tbox.biz>

On Tue, Jan 31, 2006 at 09:47:32AM +0100, Laurent Pinchart wrote:
> > No, that's good.  If you can cleanly merge the existing parsing code, by
> > all means please do so.  Thanks.
> 
> Ok I will. On which kernel tree should I base my patches on ?

I would suggest either Linus' current git tree or 2.6.16-rc1 if you don't
use git.  But please bear in mind that since this is a new feature (a new
board) it won't be submitted to Linus' tree until 2.6.17-rc1 opens up (and
if in that time, it becomes much easier to put this board under arch/powerpc
it should be done under there, instead).

-- 
Tom Rini
http://gate.crashing.org/~trini/

  reply	other threads:[~2006-01-31 14:24 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 [this message]
2006-01-31 20:31           ` Peter Korsgaard
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=20060131142433.GN22672@smtp.west.cox.net \
    --to=trini@kernel.crashing.org \
    --cc=dan@embeddedalley.com \
    --cc=laurent.pinchart@tbox.biz \
    --cc=linuxppc-embedded@ozlabs.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).