It can be expected for a boot entry to usually fail, e.g. when it checks for a removable USB drive that's not always connected. Such boot targets have the choice of either returning 0, which means it was a dry run and boot aborts or an error code, which yields an error message.
Let's handle -ENOMEDIUM specially and not print an error for it, so it can be used in such scenarios. Signed-off-by: Ahmad Fatoum <[email protected]> --- common/boot.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/common/boot.c b/common/boot.c index 9c6fc3044271..4edea682219b 100644 --- a/common/boot.c +++ b/common/boot.c @@ -151,7 +151,7 @@ int boot_entry(struct bootentry *be, int verbose, int dryrun) } ret = be->boot(be, verbose, dryrun); - if (ret) + if (ret && ret != -ENOMEDIUM) pr_err("Booting entry '%s' failed\n", be->title); return ret; -- 2.39.2
