From: Bo Shen <voice.shen@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Can I read env from RAM in uboot script?
Date: Wed, 30 Jan 2013 09:20:29 +0800 [thread overview]
Message-ID: <5108755D.8020207@atmel.com> (raw)
In-Reply-To: <1359480818.7974.184.camel@genx>
Hi John Stile,
On 01/30/2013 01:33 AM, John Stile wrote:
> That worked! Very nice! But, I had to apply the patches manually.
> Email may have messed up the patch sets with new-lines and indentation.
> Can this be added to the main stream? I am on to learning 'env import'.
> Thank you.
I will prepare the patch and send to u-boot mainline.
> If email messed it up once, I guess it could mess it up again, but I
> generated patches using:
> diff -Naur before/ after/> diff.patch
I think this can not be applied to u-boot mainline directly, because it
missed comments and author, and etc.
Best Regards,
Bo Shen
next prev parent reply other threads:[~2013-01-30 1:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-26 1:56 [U-Boot] Can I read env from RAM in uboot script? John Stile
2013-01-26 7:41 ` Wolfgang Denk
2013-01-28 21:19 ` John Stile
2013-01-28 21:48 ` Jeroen Hofstee
2013-01-28 22:01 ` Jeroen Hofstee
2013-01-29 0:25 ` John Stile
2013-01-29 9:58 ` Bo Shen
2013-01-29 17:33 ` John Stile
2013-01-30 1:20 ` Bo Shen [this message]
2013-01-29 6:37 ` 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=5108755D.8020207@atmel.com \
--to=voice.shen@atmel.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