From: Karl O. Pinc <kop@meme.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot on the POGO-E02
Date: Fri, 27 Jul 2012 09:38:13 -0500 [thread overview]
Message-ID: <1343399893.7141.0@mofo> (raw)
In-Reply-To: <F766E4F80769BD478052FB6533FA745D1A58215B10@SC-VEXCH4.marvell.com> (from prafulla@marvell.com on Fri Jul 27 00:18:48 2012)
On 07/27/2012 12:18:48 AM, Prafulla Wadaskar wrote:
>
> >
> > The appended patch is to the latest U-Boot
> > release, 2012-04. I'll see about sending
> > a patch with git as described in the
> > FAQ if I get something working.
> >
> > This patch is not to apply, but I'm
> > having a problem because the patch
> > wraps. boards.cfg contains long
> > lines, and some of the original
> > source has long lines as well.
> > What to do?
>
> You may send this patch as RFC for review.
Is there anything special, besides using git,
that I need to do to send a patch as RFC for review?
And I think I should wait to see if it works on the
device, right?
Karl <kop@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
next prev parent reply other threads:[~2012-07-27 14:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 4:57 [U-Boot] U-Boot on the POGO-E02 Karl O. Pinc
2012-07-27 5:18 ` Prafulla Wadaskar
2012-07-27 14:38 ` Karl O. Pinc [this message]
2012-07-27 5:31 ` 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=1343399893.7141.0@mofo \
--to=kop@meme.com \
--cc=u-boot@lists.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