Introduce variables whitelisting in environment
Get series with b4
b4 am 20171226122500.15dce6e4@jawaVersions newest first
- v1 Latest1 of 11 patches 0 repliesNew
1 of 11 patches is in this archive. The cover letter announces 11.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 3/11 | env: add support for whitelisting variables from secondary environments | +0 | 1 reply |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [U-Boot] [PATCH 00/11] Introduce variables whitelisting in environment
Hi Quentin,
Quoted 5 lines
2) Why do we consider
ENV_IS_NOWHEREan 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 (inenv_relocateinenv/common.c). With my patch series I guess that we could remove this fallback and forceENV_IS_NOWHEREto 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>