summaryrefslogtreecommitdiff
path: root/test/env
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2020-11-05 10:33:37 -0700
committerTom Rini <trini@konsulko.com>2020-12-04 16:09:06 -0500
commit96434a76fd254248ded19e95dc967d28e65a5edf (patch)
treef7bcdd880ec983c695273b842276bda423a72741 /test/env
parent4c450daf7d5d48ef075980e11052bf6bb28db4f6 (diff)
downloadu-boot-96434a76fd254248ded19e95dc967d28e65a5edf.tar.gz
u-boot-96434a76fd254248ded19e95dc967d28e65a5edf.tar.bz2
u-boot-96434a76fd254248ded19e95dc967d28e65a5edf.zip
env: Allow returning errors from hdelete_r()
At present this function returns 1 on success and 0 on failure. But in the latter case it provides no indication of what went wrong. If an attempt is made to delete a non-existent variable, the caller may want to ignore this error. This happens when setting a non-existent variable to "", for example. Update the function to return 0 on success and a useful error code on failure. Add a function comment too. Make sure that env_set() does not return an error if it is deleting a variable that doesn't exist. We could update env_set() to return useful error numbers also, but that is beyond the scope of this change. Signed-off-by: Simon Glass <sjg@chromium.org> wip
Diffstat (limited to 'test/env')
-rw-r--r--test/env/hashtable.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/test/env/hashtable.c b/test/env/hashtable.c
index 339cc19ba1..70102f9121 100644
--- a/test/env/hashtable.c
+++ b/test/env/hashtable.c
@@ -80,7 +80,7 @@ static int htab_create_delete(struct unit_test_state *uts,
ut_asserteq_str(key, ritem->key);
ut_asserteq_str(key, ritem->data);
- ut_asserteq(1, hdelete_r(key, htab, 0));
+ ut_asserteq(0, hdelete_r(key, htab, 0));
}
return 0;