From: Wolfgang Denk <wd@denx.de>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Tom Rini <trini@konsulko.com>,
Joe Hershberger <joe.hershberger@ni.com>
Subject: Re: [PATCH v5 4/5] env: Allow environment files to use the C preprocessor
Date: Mon, 04 Oct 2021 14:12:32 +0200 [thread overview]
Message-ID: <2673000.1633349552@gemini.denx.de> (raw)
In-Reply-To: <20211001183842.v5.4.Ie78bfbfca0d01d9cba501e127f446ec48e1f7afe@changeid>
Dear Simon Glass,
In message <20211001183842.v5.4.Ie78bfbfca0d01d9cba501e127f446ec48e1f7afe@changeid> you wrote:
> In many cases environment variables need access to the U-Boot CONFIG
> variables to select different options. Enable this so that the environment
> scripts can be as useful as the ones currently in the board config files.
>
> Also support += to allow variables to be appended to. This is needed when
> using the preprocessor.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> ---
>
> (no changes since v4)
>
> Changes in v4:
> - Add documentation in rST format instead of README
> - Move use of += to this patch
> - Explain that environment variables may not end in +
Sorry, I disagree here. There was intentionally only very little
restrictions on what a environment variable name should look like -
the only exceptions were the '=' and the NUL characters.
Adding artificial restrictions now just to enable your custom
notation for appending seems not acceptable to me. You might want
to chose a different notation or implement a proper parser instead.
Thanks.
Wolfgang Denk
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Never call a man a fool. Borrow from him.
next prev parent reply other threads:[~2021-10-04 12:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-02 0:38 [PATCH v5 0/5] env: Allow environment in text files Simon Glass
2021-10-02 0:38 ` [PATCH v5 1/5] sandbox: Drop distro_boot Simon Glass
2021-10-02 0:38 ` [PATCH v5 2/5] doc: Move environment documentation to rST Simon Glass
2021-10-04 12:05 ` Wolfgang Denk
2021-10-02 0:38 ` [PATCH v5 3/5] env: Allow U-Boot scripts to be placed in a .env file Simon Glass
2021-10-04 7:28 ` Rasmus Villemoes
2021-10-04 15:38 ` Tom Rini
2021-10-05 14:42 ` Simon Glass
2021-10-04 12:08 ` Wolfgang Denk
2021-10-05 14:42 ` Simon Glass
2021-10-05 14:55 ` Wolfgang Denk
2021-10-05 15:33 ` Simon Glass
2021-10-05 15:52 ` Tom Rini
2021-10-05 17:27 ` Simon Glass
2021-10-06 7:08 ` Wolfgang Denk
2021-10-02 0:38 ` [PATCH v5 4/5] env: Allow environment files to use the C preprocessor Simon Glass
2021-10-04 12:12 ` Wolfgang Denk [this message]
2021-10-02 0:38 ` [PATCH v5 5/5] sandbox: Use a text-based environment Simon Glass
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=2673000.1633349552@gemini.denx.de \
--to=wd@denx.de \
--cc=joe.hershberger@ni.com \
--cc=sjg@chromium.org \
--cc=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