commit | 4886ebc6df81205858a3cae693b728eece5dd4f3 | [log] [tgz] |
---|---|---|
author | Rasmus Villemoes <rasmus.villemoes@prevas.dk> | Wed Feb 19 09:47:43 2020 +0000 |
committer | Tom Rini <trini@konsulko.com> | Fri Apr 24 10:10:00 2020 -0400 |
tree | c74cefca16cde2a5e251d0ad7b20367c101d22a3 | |
parent | 89809e80bab25563d73cfdbb0c2cd25e2c20b6eb [diff] |
env/sf.c: drop private CMD_SAVEENV logic Deciding whether to compile the env_sf_save() function based solely on CONFIG_SPL_BUILD is wrong: For U-Boot proper, it leads to a build warning in case CONFIG_CMD_SAVEENV=n (because the env_save_ptr() macro causes the function to indeed not be referenced anywhere). And for SPL, when one selects CONFIG_SPL_SAVEENV, one obviously expects to actually be able to save the environment. Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>