[PATCH 1/1] log: check argument of 'log level' command

sjg at google.com sjg at google.com
Sat Jun 13 05:11:28 CEST 2020


On Sun, 31 May 2020 at 07:44, Heinrich Schuchardt <xypron.glpk at gmx.de> wrote:
>
> Check that the argument provided to the 'log level' command is in the range
> between zero and CONFIG_LOG_MAX_LEVEL.
>
> Signed-off-by: Heinrich Schuchardt <xypron.glpk at gmx.de>
> ---
>  cmd/log.c | 14 +++++++++++---
>  1 file changed, 11 insertions(+), 3 deletions(-)

Reviewed-by: Simon Glass <sjg at chromium.org>

Then we should have a little test for the log command, perhaps
run_command() and then check that the default log level is set (or
not, on error).

Applied to u-boot-dm, thanks!


More information about the U-Boot mailing list