summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2016-01-17 16:11:29 -0700
committerBin Meng <bmeng.cn@gmail.com>2016-01-24 12:08:17 +0800
commit8b674418e0250aae9748d9b53fe4c9d9607b7e36 (patch)
tree4f6de5c568cee8cbfe3f14c2910eecda4e60cdbd
parentafd5d50c127da6457ce75b534717b954e07f606c (diff)
downloadu-boot-imx-8b674418e0250aae9748d9b53fe4c9d9607b7e36.zip
u-boot-imx-8b674418e0250aae9748d9b53fe4c9d9607b7e36.tar.gz
u-boot-imx-8b674418e0250aae9748d9b53fe4c9d9607b7e36.tar.bz2
x86: Don't show an error when the MRC cache is up to date
When the final MRC cache record is the same as the one we want to write, we skip writing since there is no point. This is normal behaviour. Avoiding printing an error when this happens. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
-rw-r--r--arch/x86/lib/mrccache.c6
1 files changed, 5 insertions, 1 deletions
diff --git a/arch/x86/lib/mrccache.c b/arch/x86/lib/mrccache.c
index 53a1259..67bace4 100644
--- a/arch/x86/lib/mrccache.c
+++ b/arch/x86/lib/mrccache.c
@@ -243,8 +243,12 @@ int mrccache_save(void)
goto err_entry;
data = (struct mrc_data_container *)gd->arch.mrc_output;
ret = mrccache_update(sf, &entry, data);
- if (!ret)
+ if (!ret) {
debug("Saved MRC data with checksum %04x\n", data->checksum);
+ } else if (ret == -EEXIST) {
+ debug("MRC data is the same as last time, skipping save\n");
+ ret = 0;
+ }
err_entry:
if (ret)