From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2] Document config_distro_bootcmd environment variables for interactive booting.
Date: Mon, 23 Mar 2015 13:34:34 -0600 [thread overview]
Message-ID: <55106ACA.1020203@wwwdotorg.org> (raw)
In-Reply-To: <1426943738-8326-2-git-send-email-merker@debian.org>
On 03/21/2015 07:15 AM, Karsten Merker wrote:
> config_distro_bootcmd.h defines a common boot environment for multiple
> platforms, including several environment variables that are intended for
> interactive use by an end-user. Document which variables are considered
> public interfaces that must remain compatible in future u-boot versions.
Acked-by: Stephen Warren <swarren@nvidia.com>
next prev parent reply other threads:[~2015-03-23 19:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 23:31 [U-Boot] [ANN] U-Boot v2015.04-rc3 released Tom Rini
[not found] ` <20150304195337.GA4874@excalibur.cnev.de>
[not found] ` <20150311202046.GA8890@excalibur.cnev.de>
2015-03-11 20:31 ` [U-Boot] Regression in bootcmd handling in v2015.04-rc3? Stephen Warren
[not found] ` <20150311212100.GA9680@excalibur.cnev.de>
2015-03-11 21:35 ` Stephen Warren
[not found] ` <20150311214825.GB9680@excalibur.cnev.de>
2015-03-17 16:16 ` Tom Rini
2015-03-19 19:41 ` [U-Boot] config_distro_bootcmd and boot environment (was: Regression in bootcmd handling in v2015.04-rc3?) Karsten Merker
2015-03-19 19:41 ` [U-Boot] [PATCH] Document config_distro_bootcmd environment variables for interactive booting Karsten Merker
2015-03-19 19:53 ` Stephen Warren
[not found] ` <20150319205334.GB8313@excalibur.cnev.de>
2015-03-19 21:02 ` Stephen Warren
2015-03-21 13:15 ` [U-Boot] [PATCH V2] " Karsten Merker
2015-03-21 13:15 ` Karsten Merker
2015-03-23 19:34 ` Stephen Warren [this message]
2015-03-28 18:09 ` [U-Boot] [U-Boot, " Tom Rini
2015-03-11 20:31 ` [U-Boot] Regression in bootcmd handling in v2015.04-rc3? (was: [ANN] U-Boot v2015.04-rc3 released) Tom Rini
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=55106ACA.1020203@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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