From: Xie XiuQi <xiexiuqi@huawei.com>
To: akpm@linux-foundation.org, n-horiguchi@ah.jp.nec.com
Cc: rostedt@goodmis.org, gong.chen@linux.intel.com, mingo@redhat.com,
bp@suse.de, tony.luck@intel.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, jingle.chen@huawei.com, sfr@canb.auug.org.au,
rdunlap@infradead.org, jim.epost@gmail.com
Subject: [PATCH v6 4/5] tracing: fix build error in mm/memory-failure.c
Date: Thu, 21 May 2015 11:41:24 +0800 [thread overview]
Message-ID: <1432179685-11369-5-git-send-email-xiexiuqi@huawei.com> (raw)
In-Reply-To: <1432179685-11369-1-git-send-email-xiexiuqi@huawei.com>
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@infradead.org>
Reported-by: Jim Davis <jim.epost@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Chen Gong <gong.chen@linux.intel.com>
Acked-by: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Signed-off-by: Xie XiuQi <xiexiuqi@huawei.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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-05-21 3:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 3:41 [PATCH v6 0/5] tracing: add trace event for memory-failure Xie XiuQi
2015-05-21 3:41 ` [PATCH v6 1/5] memory-failure: export page_type and action result Xie XiuQi
2015-05-21 3:41 ` [PATCH v6 2/5] memory-failure: change type of action_result's param 3 to enum Xie XiuQi
2015-05-21 3:41 ` [PATCH v6 3/5] tracing: add trace event for memory-failure Xie XiuQi
2015-05-21 3:41 ` Xie XiuQi [this message]
2015-05-21 3:41 ` [PATCH v6 5/5] trace, ras: move ras_event.h under include/trace/events Xie XiuQi
2015-05-21 9:24 ` Borislav Petkov
2015-05-21 13:01 ` Steven Rostedt
2015-05-21 23:00 ` Naoya Horiguchi
2015-05-21 23:28 ` [PATCH v6 0/5] tracing: add trace event for memory-failure Naoya Horiguchi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1432179685-11369-5-git-send-email-xiexiuqi@huawei.com \
--to=xiexiuqi@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=bp@suse.de \
--cc=gong.chen@linux.intel.com \
--cc=jim.epost@gmail.com \
--cc=jingle.chen@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
--cc=tony.luck@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox