From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH] Allow providing default environment from file
Date: Mon, 19 Mar 2018 09:30:11 -0400 [thread overview]
Message-ID: <20180319133011.GR4418@bill-the-cat.ec.rr.com> (raw)
In-Reply-To: <20180124095559.28317-1-rasmus.villemoes@prevas.dk>
On Wed, Jan 24, 2018 at 10:55:59AM +0100, Rasmus Villemoes wrote:
> It is sometimes useful to be able to define the entire default
> environment in an external file. This implements a Kconfig option for
> allowing that.
>
> It is somewhat annoying to have two visible Kconfig options; it would
> probably be more user-friendly to just have the string option (with
> empty string obviously meaning not to use this feature). But then we'd
> also need a hidden CONFIG that we can use in the #ifdef in
> env_default.h, and I don't think one can set a def_bool based on
> whether a string-valued config is empty or not.
>
> I've tried to make the accepted format the same as the one the
> mkenvimage tool accepts. I have no idea how portable the sed script
> implementing the "allow embedded newlines in values" is. Nor do I know
> if one can expect xxd to be available.
>
> Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
> ---
> Makefile | 16 ++++++++++++++++
> env/Kconfig | 18 ++++++++++++++++++
> include/env_default.h | 4 ++++
> 3 files changed, 38 insertions(+)
Conceptually, this is fine. But can you please re-word the commit
message and put some of the commentary below the --- ? Also, in general
we do a pair of CONFIG_USE_xxx and CONFIG_xxx, so you might need to
re-word the rest of the option name a bit too to match that. Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180319/5e42360a/attachment.sig>
next prev parent reply other threads:[~2018-03-19 13:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 9:55 [U-Boot] [RFC PATCH] Allow providing default environment from file Rasmus Villemoes
2018-01-25 9:30 ` Lukasz Majewski
2018-01-25 10:04 ` Rasmus Villemoes
2018-01-25 10:26 ` Lukasz Majewski
2018-01-26 13:22 ` Sean Nyekjaer
2018-02-02 20:15 ` Rasmus Villemoes
2018-03-19 7:17 ` Sean Nyekjær
2018-03-19 13:30 ` Tom Rini [this message]
2018-03-20 10:38 ` [U-Boot] [PATCH v2] " Rasmus Villemoes
2018-03-20 14:20 ` Lukasz Majewski
2018-03-20 14:47 ` Rasmus Villemoes
2018-04-04 8:40 ` Rasmus Villemoes
2018-04-07 13:25 ` [U-Boot] [U-Boot, " 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=20180319133011.GR4418@bill-the-cat.ec.rr.com \
--to=trini@konsulko.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