[PATCH 2/5] cmd: env: use ENV_IS_IN_DEVICE in env info
Simon Glass
sjg at chromium.org
Thu Jan 30 03:17:47 CET 2020
On Fri, 24 Jan 2020 at 05:34, Patrick Delaunay <patrick.delaunay at st.com> wrote:
>
> Use the define ENV_IS_IN_DEVICE to test if one the
> CONFIG_ENV_IS_IN_... is defined and correct the detection of
> persistent storage support in the command "env info"
> if CONFIG_ENV_IS_NOWHERE is activated.
>
> Since commit 60d5ed2593c9 ("env: allow ENV_IS_NOWHERE with
> other storage target") test CONFIG_ENV_IS_NOWHERE is not
> enough; see also commit 953db29a1e9c6 ("env: enable saveenv
> command when one CONFIG_ENV_IS_IN is activated").
>
> This patch avoids issue for this command in stm32mp1 platform.
>
> Signed-off-by: Patrick Delaunay <patrick.delaunay at st.com>
> ---
>
> cmd/nvedit.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Simon Glass <sjg at chromium.org>
We should add more tests for the environment functionality.
More information about the U-Boot
mailing list