linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddedalley.com>
To: Laurent Pinchart <laurent.pinchart@tbox.biz>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [RFC] arch/ppc/boot/simple/embed_boot.c : Merging all keyvals parsing code
Date: Wed, 25 Jan 2006 07:48:59 -0800	[thread overview]
Message-ID: <bc2424c0c5f69931784ea76791f8ee39@embeddedalley.com> (raw)
In-Reply-To: <200601251215.10816.laurent.pinchart@tbox.biz>


On Jan 25, 2006, at 3:15 AM, Laurent Pinchart wrote:

> Should I submit a patch, or leave the code as it is ?

Port Das U-Boot.


	-- Dan

  reply	other threads:[~2006-01-25 15:55 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 [this message]
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
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=bc2424c0c5f69931784ea76791f8ee39@embeddedalley.com \
    --to=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).