[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1432179685-11369-5-git-send-email-xiexiuqi@huawei.com>
Date: Thu, 21 May 2015 11:41:24 +0800
From: Xie XiuQi <xiexiuqi@...wei.com>
To: <akpm@...ux-foundation.org>, <n-horiguchi@...jp.nec.com>
CC: <rostedt@...dmis.org>, <gong.chen@...ux.intel.com>,
<mingo@...hat.com>, <bp@...e.de>, <tony.luck@...el.com>,
<linux-kernel@...r.kernel.org>, <linux-mm@...ck.org>,
<jingle.chen@...wei.com>, <sfr@...b.auug.org.au>,
<rdunlap@...radead.org>, <jim.epost@...il.com>
Subject: [PATCH v6 4/5] tracing: fix build error in mm/memory-failure.c
next-20150515 fails to build on i386 with the following error:
mm/built-in.o: In function `action_result':
memory-failure.c:(.text+0x344a5): undefined reference to `__tracepoint_memory_failure_event'
memory-failure.c:(.text+0x344d5): undefined reference to `__tracepoint_memory_failure_event'
memory-failure.c:(.text+0x3450c): undefined reference to `__tracepoint_memory_failure_event'
trace_memory_failure_event depends on CONFIG_RAS,
so add 'select RAS' in mm/Kconfig to avoid this error.
Reported-by: Randy Dunlap <rdunlap@...radead.org>
Reported-by: Jim Davis <jim.epost@...il.com>
Cc: Steven Rostedt <rostedt@...dmis.org>
Cc: Chen Gong <gong.chen@...ux.intel.com>
Acked-by: Naoya Horiguchi <n-horiguchi@...jp.nec.com>
Signed-off-by: Xie XiuQi <xiexiuqi@...wei.com>
---
mm/Kconfig | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/mm/Kconfig b/mm/Kconfig
index 390214d..c180af8 100644
--- a/mm/Kconfig
+++ b/mm/Kconfig
@@ -368,6 +368,7 @@ config MEMORY_FAILURE
depends on ARCH_SUPPORTS_MEMORY_FAILURE
bool "Enable recovery from hardware memory errors"
select MEMORY_ISOLATION
+ select RAS
help
Enables code to recover from some memory failures on systems
with MCA recovery. This allows a system to continue running
--
1.7.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists