Hi Simon, > From: Simon Glass <s...@chromium.org> > Sent: jeudi 30 janvier 2020 03:18 > > On Fri, 24 Jan 2020 at 05:34, Patrick Delaunay <patrick.delau...@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.delau...@st.com> > > --- > > > > cmd/nvedit.c | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > Reviewed-by: Simon Glass <s...@chromium.org> > > We should add more tests for the environment functionality.
Sorry for the delay, I need to activate a location in sandbox to test this feature.... I am working on a other serie for it (I am trying to add test for env in EXT4). Patrick