| Message ID | 20200219094726.26798-2-rasmus.villemoes@prevas.dk |
|---|---|
| State | Superseded |
| Headers | show |
| Series | CMD_SAVEENV ifdef cleanup | expand |
On Wed, Feb 19, 2020 at 09:47:39AM +0000, Rasmus Villemoes wrote: > Currently, testing whether to compile in support for saving the > environment is a bit awkward when one needs to take SPL_SAVEENV into > account, and quite a few storage drivers currently do not honour > SPL_SAVEENV. > > To make it a bit easier to decide whether environment saving should be > enabled, introduce SAVEENV as an alias for the CMD_SAVEENV > symbol. Then one can simply use > > CONFIG_IS_ENABLED(SAVEENV) > > Signed-off-by: Rasmus Villemoes <rasmus.villemoes at prevas.dk> Applied to u-boot/master, thanks!
diff --git a/env/Kconfig b/env/Kconfig index 0d6f559b39..969308fe6c 100644 --- a/env/Kconfig +++ b/env/Kconfig @@ -3,6 +3,9 @@ menu "Environment" config ENV_SUPPORT def_bool y +config SAVEENV + def_bool y if CMD_SAVEENV + config ENV_IS_NOWHERE bool "Environment is not stored" default y if !ENV_IS_IN_EEPROM && !ENV_IS_IN_EXT4 && \
Currently, testing whether to compile in support for saving the environment is a bit awkward when one needs to take SPL_SAVEENV into account, and quite a few storage drivers currently do not honour SPL_SAVEENV. To make it a bit easier to decide whether environment saving should be enabled, introduce SAVEENV as an alias for the CMD_SAVEENV symbol. Then one can simply use CONFIG_IS_ENABLED(SAVEENV) Signed-off-by: Rasmus Villemoes <rasmus.villemoes at prevas.dk> --- env/Kconfig | 3 +++ 1 file changed, 3 insertions(+)