All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xie XiuQi <xiexiuqi@huawei.com>
To: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Linux MM <linux-mm@kvack.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jim Davis <jim.epost@gmail.com>,
	Chen Gong <gong.chen@linux.intel.com>
Subject: Re: linux-next: Tree for May 18 (mm/memory-failure.c)
Date: Wed, 20 May 2015 14:19:21 +0800	[thread overview]
Message-ID: <555C2769.1000608@huawei.com> (raw)
In-Reply-To: <20150520060900.GD27005@hori1.linux.bs1.fc.nec.co.jp>

On 2015/5/20 14:09, Naoya Horiguchi wrote:
> On Wed, May 20, 2015 at 01:41:57PM +0800, Xie XiuQi wrote:
> ...
>>
>> 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?
> 
> Yes, thank you for digging.
> I posted exactly the same patch just miniutes ago, but yours is a bit
> earlier than mine, so you take the authorship :)

Thanks ;-)

> 
>> ---
>> From 99d91a901142b17287432b00169ac6bd9d87b489 Mon Sep 17 00:00:00 2001
>> From: Xie XiuQi <xiexiuqi@huawei.com>
>> Date: Thu, 21 May 2015 13:11:38 +0800
>> Subject: [PATCH] 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@infradead.org>
>> Reported-by: Jim Davis <jim.epost@gmail.com>
>> Cc: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
>> Cc: Steven Rostedt <rostedt@goodmis.org>
>> Cc: Chen Gong <gong.chen@linux.intel.com>
>> Signed-off-by: Xie XiuQi <xiexiuqi@huawei.com>
> 
> Acked-by: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
> 
> Thanks,
> Naoya
> .
> 

WARNING: multiple messages have this Message-ID (diff)
From: Xie XiuQi <xiexiuqi@huawei.com>
To: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Linux MM <linux-mm@kvack.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jim Davis <jim.epost@gmail.com>,
	Chen Gong <gong.chen@linux.intel.com>
Subject: Re: linux-next: Tree for May 18 (mm/memory-failure.c)
Date: Wed, 20 May 2015 14:19:21 +0800	[thread overview]
Message-ID: <555C2769.1000608@huawei.com> (raw)
In-Reply-To: <20150520060900.GD27005@hori1.linux.bs1.fc.nec.co.jp>

On 2015/5/20 14:09, Naoya Horiguchi wrote:
> On Wed, May 20, 2015 at 01:41:57PM +0800, Xie XiuQi wrote:
> ...
>>
>> 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?
> 
> Yes, thank you for digging.
> I posted exactly the same patch just miniutes ago, but yours is a bit
> earlier than mine, so you take the authorship :)

Thanks ;-)

> 
>> ---
>> From 99d91a901142b17287432b00169ac6bd9d87b489 Mon Sep 17 00:00:00 2001
>> From: Xie XiuQi <xiexiuqi@huawei.com>
>> Date: Thu, 21 May 2015 13:11:38 +0800
>> Subject: [PATCH] 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@infradead.org>
>> Reported-by: Jim Davis <jim.epost@gmail.com>
>> Cc: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
>> Cc: Steven Rostedt <rostedt@goodmis.org>
>> Cc: Chen Gong <gong.chen@linux.intel.com>
>> Signed-off-by: Xie XiuQi <xiexiuqi@huawei.com>
> 
> Acked-by: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
> 
> Thanks,
> Naoya
> .
> 


--
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>

  reply	other threads:[~2015-05-20  6:19 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18  8:52 linux-next: Tree for May 18 Stephen Rothwell
2015-05-18 15:20 ` linux-next: Tree for May 18 (mm/memory-failure.c) Randy Dunlap
2015-05-19  2:49   ` Naoya Horiguchi
2015-05-19  2:49     ` Naoya Horiguchi
2015-05-19  4:40     ` Randy Dunlap
2015-05-19  4:40       ` Randy Dunlap
2015-05-19 13:46     ` Steven Rostedt
2015-05-19 13:46       ` Steven Rostedt
2015-05-20  5:36       ` Naoya Horiguchi
2015-05-20  5:36         ` Naoya Horiguchi
2015-05-20  6:01         ` [PATCH v2 1/2] ras: hwpoison: fix build failure around trace_memory_failure_event Naoya Horiguchi
2015-05-20  6:01           ` Naoya Horiguchi
2015-05-20  6:03           ` [PATCH 2/2] trace, ras: move ras_event.h under include/trace/events Naoya Horiguchi
2015-05-20  6:03             ` Naoya Horiguchi
2015-05-20  7:16             ` Naoya Horiguchi
2015-05-20  7:16               ` Naoya Horiguchi
2015-05-20  8:15               ` [PATCH v2] " Naoya Horiguchi
2015-05-20  8:15                 ` Naoya Horiguchi
2015-05-20  5:41     ` linux-next: Tree for May 18 (mm/memory-failure.c) Xie XiuQi
2015-05-20  5:41       ` Xie XiuQi
2015-05-20  6:09       ` Naoya Horiguchi
2015-05-20  6:09         ` Naoya Horiguchi
2015-05-20  6:19         ` Xie XiuQi [this message]
2015-05-20  6:19           ` Xie XiuQi
2015-05-20 20:03       ` Andrew Morton
2015-05-20 20:03         ` Andrew Morton
2015-05-21  0:17         ` Stephen Rothwell
2015-05-21  8:23           ` Stephen Rothwell

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=555C2769.1000608@huawei.com \
    --to=xiexiuqi@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=gong.chen@linux.intel.com \
    --cc=jim.epost@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=rdunlap@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.