linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Xie XiuQi <xiexiuqi@huawei.com>
Cc: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
	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>,
	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 13:03:20 -0700	[thread overview]
Message-ID: <20150520130320.1fc1bd7b1c26dae15c5946c5@linux-foundation.org> (raw)
In-Reply-To: <555C1EA5.3080700@huawei.com>

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.

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

  parent reply	other threads:[~2015-05-20 20:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150518185226.23154d47@canb.auug.org.au>
2015-05-18 15:20 ` Randy Dunlap
2015-05-19  2:49   ` Naoya Horiguchi
2015-05-19  4:40     ` Randy Dunlap
2015-05-19 13:46     ` Steven Rostedt
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:03           ` [PATCH 2/2] trace, ras: move ras_event.h under include/trace/events Naoya Horiguchi
2015-05-20  7:16             ` Naoya Horiguchi
2015-05-20  8:15               ` [PATCH v2] " Naoya Horiguchi
2015-05-20  5:41     ` linux-next: Tree for May 18 (mm/memory-failure.c) Xie XiuQi
2015-05-20  6:09       ` Naoya Horiguchi
2015-05-20  6:19         ` Xie XiuQi
2015-05-20 20:03       ` Andrew Morton [this message]
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=20150520130320.1fc1bd7b1c26dae15c5946c5@linux-foundation.org \
    --to=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 \
    --cc=xiexiuqi@huawei.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