From dd03af6a9a56a1aed1ebe1a591caac2fa699bd52 Mon Sep 17 00:00:00 2001 From: Namyoon Woo Date: Tue, 23 Jul 2019 13:37:22 -0700 Subject: 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 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/1715910 Reviewed-by: Vadim Bendebury --- common/new_nvmem.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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); } -- cgit v1.2.1