Re: linux-next: Tree for May 18 (mm/memory-failure.c)
From: Andrew Morton <akpm@linux-foundation.org>
Date: 2015-05-20 20:03:25
Also in:
linux-mm, lkml
On Wed, 20 May 2015 13:41:57 +0800 Xie XiuQi [off-list ref] wrote:
On 2015/5/19 10:49, Naoya Horiguchi wrote:quoted
On Mon, May 18, 2015 at 08:20:07AM -0700, Randy Dunlap wrote:quoted
On 05/18/15 01:52, Stephen Rothwell wrote:quoted
Hi all, Changes since 20150515:on i386: 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'Thanks for the reporting, Randy. Here is a patch for this problem, could you try it?Hi Naoya, This patch will introduce another build error with attched config file. drivers/built-in.o:(__tracepoints+0x500): multiple definition of `__tracepoint_aer_event' mm/built-in.o:(__tracepoints+0x398): first defined here drivers/built-in.o:(__tracepoints+0x4ec): multiple definition of `__tracepoint_memory_failure_event' mm/built-in.o:(__tracepoints+0x384): first defined here drivers/built-in.o:(__tracepoints+0x514): multiple definition of `__tracepoint_mc_event' mm/built-in.o:(__tracepoints+0x3ac): first defined here drivers/built-in.o:(__tracepoints+0x528): multiple definition of `__tracepoint_extlog_mem_event' mm/built-in.o:(__tracepoints+0x3c0): first defined here make: *** [vmlinux] Error 1 Is this one better?
I'm lost. I dropped memory-failure-export-page_type-and-action-result.patch memory-failure-change-type-of-action_results-param-3-to-enum.patch tracing-add-trace-event-for-memory-failure.patch Let's start again. -- 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>