Stop using builtin_run_command()
Boards can select either the 'built-in' parser or the hush parser. We should not call builtin_run_command() if we are using the hush parser. We use run_command() instead, since it knows how to call the correct parser. Signed-off-by: Simon Glass <sjg@chromium.org> Acked-by: Mike Frysinger <vapier@gentoo.org>
This commit is contained in:
committed by
Wolfgang Denk
parent
009dde1955
commit
5307153236
@@ -226,12 +226,7 @@ static void kw_sysrst_action(void)
|
||||
}
|
||||
|
||||
debug("Starting %s process...\n", __FUNCTION__);
|
||||
#if !defined(CONFIG_SYS_HUSH_PARSER)
|
||||
ret = builtin_run_command(s, 0);
|
||||
#else
|
||||
ret = parse_string_outer(s, FLAG_PARSE_SEMICOLON
|
||||
| FLAG_EXIT_FROM_LOOP);
|
||||
#endif
|
||||
ret = run_command(s, 0);
|
||||
if (ret < 0)
|
||||
debug("Error.. %s failed\n", __FUNCTION__);
|
||||
else
|
||||
|
||||
Reference in New Issue
Block a user