From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 00/11] Introduce variables whitelisting in environment
Date: Tue, 26 Dec 2017 12:25:00 +0100 [thread overview]
Message-ID: <20171226122500.15dce6e4@jawa> (raw)
In-Reply-To: <cover.85b371954a92a5f2af96f471effacfaedd8b5271.1513975247.git-series.quentin.schulz@free-electrons.com>
Hi Quentin,
> 2) Why do we consider ENV_IS_NOWHERE an invalid environment? The only
> place I found a use for it was to just say that if the environment is
> invalid, we should set to default environment (in env_relocate in
> env/common.c). With my patch series I guess that we could remove this
> fallback and force ENV_IS_NOWHERE to be always there.
It is perfectly valid to use ENV_IS_NOWHERE to get envs from hardcoded
board file (for example for production u-boot).
However, some time ago we had extension in the envs to get the support
for envs from different mediums (with set priorities).
Best regards,
Lukasz Majewski
--
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 at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20171226/1b8894d9/attachment.sig>
next prev parent reply other threads:[~2017-12-26 11:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 21:13 [U-Boot] [PATCH 00/11] Introduce variables whitelisting in environment Quentin Schulz
2017-12-22 21:13 ` [U-Boot] [PATCH 01/11] env: fix ret not being set and fails when no env could have been init Quentin Schulz
2017-12-22 21:13 ` [U-Boot] [PATCH 02/11] lib: hashtable: support whitelisting env variables Quentin Schulz
2017-12-22 21:13 ` [U-Boot] [PATCH 03/11] env: add support for whitelisting variables from secondary environments Quentin Schulz
2017-12-26 11:21 ` Lukasz Majewski
2018-01-03 11:07 ` Quentin Schulz
2017-12-22 21:13 ` [U-Boot] [PATCH 04/11] env: make nowhere an env medium like the others Quentin Schulz
2017-12-22 21:13 ` [U-Boot] [PATCH 05/11] cmd: saveenv: enable the saveenv command when ENV_IS_NOWHERE is defined Quentin Schulz
2017-12-22 21:13 ` [U-Boot] [PATCH 06/11] env: add env_driver to env_driver functions' arguments Quentin Schulz
2017-12-22 21:13 ` [U-Boot] [PATCH 07/11] env: gd flags without ENV_READY is enough to discriminate in Quentin Schulz
2017-12-22 21:13 ` [U-Boot] [PATCH 08/11] env: add env_driver parameter to env_import_redund Quentin Schulz
2017-12-22 21:13 ` [U-Boot] [PATCH 09/11] env: make env_locations a global variable Quentin Schulz
2017-12-22 21:13 ` [U-Boot] [PATCH 10/11] env: introducing env_info struct for storing info per env Quentin Schulz
2017-12-22 21:13 ` [U-Boot] [PATCH 11/11] env: store information about each environment in gd Quentin Schulz
2017-12-26 11:25 ` Lukasz Majewski [this message]
2017-12-29 3:13 ` [U-Boot] [PATCH 00/11] Introduce variables whitelisting in environment Simon Glass
2018-01-03 9:18 ` Quentin Schulz
2018-01-08 4:50 ` 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=20171226122500.15dce6e4@jawa \
--to=lukma@denx.de \
--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