summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNamyoon Woo <namyoon@chromium.org>2019-07-23 13:37:22 -0700
committerCommit Bot <commit-bot@chromium.org>2019-07-24 00:27:46 +0000
commitdd03af6a9a56a1aed1ebe1a591caac2fa699bd52 (patch)
treeba27f6dc9659df66b3a67456868ae6820c41ec23
parentc7a2862144ad8ff996c232a2b1eeaef4aae70b26 (diff)
downloadchrome-ec-dd03af6a9a56a1aed1ebe1a591caac2fa699bd52.tar.gz
cr50: minor fix in neglecting 'failure type' in NVMEM flash log
report_no_payload_failure() function gets an input 'failure type', but it always marks failure type as 'inconsistent flash content' instead of that input. BUG=None BRANCH=cr50, cr50-mp TEST=none Change-Id: I5bac69478416eeabf735faf5333f5f7eaa98b54e Signed-off-by: Namyoon Woo <namyoon@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/1715910 Reviewed-by: Vadim Bendebury <vbendeb@chromium.org>
-rw-r--r--common/new_nvmem.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/common/new_nvmem.c b/common/new_nvmem.c
index d9461736dc..a9e0435893 100644
--- a/common/new_nvmem.c
+++ b/common/new_nvmem.c
@@ -383,7 +383,7 @@ static void report_no_payload_failure(enum nvmem_failure_type type)
{
struct nvmem_failure_payload fp;
- fp.failure_type = NVMEMF_INCONSISTENT_FLASH_CONTENTS;
+ fp.failure_type = type;
report_failure(&fp, 0);
}