From: kbuild test robot <lkp@intel.com>
To: Li Bin <huawei.libin@huawei.com>
Cc: kbuild-all@01.org, catalin.marinas@arm.com, will.deacon@arm.com,
rostedt@goodmis.org, takahiro.akashi@linaro.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, guohanjun@huawei.com,
dingtianhong@huawei.com, huawei.libin@huawei.com,
zhouchengming1@huawei.com
Subject: Re: [PATCH] recordmcount: arm64: replace the ignored mcount call into nop
Date: Thu, 29 Oct 2015 21:35:42 +0800 [thread overview]
Message-ID: <201510292118.ZYBYzBGa%fengguang.wu@intel.com> (raw)
In-Reply-To: <1446019445-14421-1-git-send-email-huawei.libin@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
Hi Li,
[auto build test ERROR on arm64/for-next/core -- if it's inappropriate base, please suggest rules for selecting the more suitable base]
url: https://github.com/0day-ci/linux/commits/Li-Bin/recordmcount-arm64-replace-the-ignored-mcount-call-into-nop/20151028-160846
config: arm64-allmodconfig (attached as .config)
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=arm64
All errors (new ones prefixed by >>):
>> /bin/bash: line 1: 117734 Segmentation fault ./scripts/recordmcount "arch/arm64/kernel/traps.o"
--
>> /bin/bash: line 1: 113824 Segmentation fault ./scripts/recordmcount "arch/arm64/mm/fault.o"
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 45574 bytes --]
next prev parent reply other threads:[~2015-10-29 13:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 8:04 Li Bin
2015-10-28 8:16 ` Steven Rostedt
2015-10-28 11:58 ` Will Deacon
2015-10-29 5:43 ` AKASHI Takahiro
2015-10-29 13:35 ` kbuild test robot [this message]
2015-10-29 15:09 ` Will Deacon
2015-10-30 6:00 ` libin
2015-11-02 18:26 ` Steven Rostedt
2015-11-02 18:28 ` Will Deacon
2015-11-02 19:34 ` Steven Rostedt
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=201510292118.ZYBYzBGa%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=catalin.marinas@arm.com \
--cc=dingtianhong@huawei.com \
--cc=guohanjun@huawei.com \
--cc=huawei.libin@huawei.com \
--cc=kbuild-all@01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=takahiro.akashi@linaro.org \
--cc=will.deacon@arm.com \
--cc=zhouchengming1@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
all inboxes | Powered by JetHome®