summaryrefslogtreecommitdiff
path: root/common/image-fit.c
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2014-06-12 07:24:45 -0600
committerTom Rini <trini@ti.com>2014-06-19 11:18:58 -0400
commit12df2abe3e159d622701611766c085b860329f78 (patch)
treec8e3881b3ea7cddd949552d48fd9c4771e9a74cf /common/image-fit.c
parentba923cab0006838eb726e40207501ddf16eabd80 (diff)
downloadu-boot-imx-12df2abe3e159d622701611766c085b860329f78.zip
u-boot-imx-12df2abe3e159d622701611766c085b860329f78.tar.gz
u-boot-imx-12df2abe3e159d622701611766c085b860329f78.tar.bz2
Reverse the meaning of the fit_config_verify() return code
It is more common to have 0 mean OK, and -ve mean error. Change this function to work the same way to avoid confusion. Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'common/image-fit.c')
-rw-r--r--common/image-fit.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/common/image-fit.c b/common/image-fit.c
index 732505a..40c7e27 100644
--- a/common/image-fit.c
+++ b/common/image-fit.c
@@ -1534,7 +1534,7 @@ int fit_image_load(bootm_headers_t *images, const char *prop_name, ulong addr,
images->fit_uname_cfg = fit_uname_config;
if (IMAGE_ENABLE_VERIFY && images->verify) {
puts(" Verifying Hash Integrity ... ");
- if (!fit_config_verify(fit, cfg_noffset)) {
+ if (fit_config_verify(fit, cfg_noffset)) {
puts("Bad Data Hash\n");
bootstage_error(bootstage_id +
BOOTSTAGE_SUB_HASH);