From 45a225b05dbc22c5aff3c8baf927a68142f6be86 Mon Sep 17 00:00:00 2001
From: Stefan Reinauer <reinauer@chromium.org>
Date: Mon, 16 Mar 2015 16:47:39 -0700
Subject: elog: Fix compilation with CONFIG_CHROMEOS enabled

On ChromeOS devices the ELOG section size and offset are
provided by the FMAP, rather than KConfig. Some upstream
refactoring broke compilation in that case.

Change-Id: I8b08daa327726218815855c7c2be45f44fcffeed
Signed-off-by: Stefan Reinauer <reinauer@google.com>
Reviewed-on: http://review.coreboot.org/8700
Tested-by: build bot (Jenkins)
Reviewed-by: Aaron Durbin <adurbin@google.com>
---
 src/drivers/elog/elog.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'src/drivers/elog')

diff --git a/src/drivers/elog/elog.c b/src/drivers/elog/elog.c
index 77019065ed..8bc8a0753a 100644
--- a/src/drivers/elog/elog.c
+++ b/src/drivers/elog/elog.c
@@ -37,7 +37,7 @@
 
 #include <vendorcode/google/chromeos/fmap.h>
 
-#if CONFIG_ELOG_FLASH_BASE == 0
+#if !IS_ENABLED(CONFIG_CHROMEOS) && CONFIG_ELOG_FLASH_BASE == 0
 #error "CONFIG_ELOG_FLASH_BASE is invalid"
 #endif
 #if CONFIG_ELOG_FULL_THRESHOLD >= CONFIG_ELOG_AREA_SIZE
-- 
cgit v1.2.3