lkml.org 
[lkml]   [2015]   [May]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: linux-next: Tree for May 18 (mm/memory-failure.c)
On Wed, 20 May 2015 13:41:57 +0800 Xie XiuQi <xiexiuqi@huawei.com> wrote:

> On 2015/5/19 10:49, Naoya Horiguchi wrote:
> > On Mon, May 18, 2015 at 08:20:07AM -0700, Randy Dunlap wrote:
> >> On 05/18/15 01:52, Stephen Rothwell wrote:
> >>> 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.


\
 
 \ /
  Last update: 2015-05-20 22:41    [W:0.073 / U:0.296 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site