From: kbuild test robot <lkp@intel.com>
To: Jeffrey Merkey <jeffmerkey@gmail.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
ralf@linux-mips.org, james.hogan@imgtec.com, linux.mdb@gmail.com,
linux-mips@linux-mips.org
Subject: Re: [PATCH 21/31] Add debugger entry points for MIPS
Date: Fri, 29 Jan 2016 05:41:06 +0800 [thread overview]
Message-ID: <201601290507.6eVJpNrW%fengguang.wu@intel.com> (raw)
In-Reply-To: <1454010437-29265-1-git-send-email-jeffmerkey@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2270 bytes --]
Hi Jeffrey,
[auto build test ERROR on v4.5-rc1]
[also build test ERROR on next-20160128]
[cannot apply to tip/x86/core]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Jeffrey-Merkey/Add-hard-soft-lockup-debugger-entry-points/20160129-035852
config: mips-jz4740 (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=mips
All errors (new ones prefixed by >>):
kernel/sys.o: In function `arch_breakpoint':
>> sys.c:(.text+0x880): multiple definition of `arch_breakpoint'
kernel/sysctl.o:sysctl.c:(.text+0x134c): first defined here
kernel/sys.o: In function `arch_breakpoint':
>> sys.c:(.text+0x884): multiple definition of `breakinst'
kernel/sysctl.o:sysctl.c:(.text+0x1350): first defined here
kernel/notifier.o: In function `arch_breakpoint':
notifier.c:(.text+0x678): multiple definition of `arch_breakpoint'
kernel/sysctl.o:sysctl.c:(.text+0x134c): first defined here
kernel/notifier.o: In function `arch_breakpoint':
notifier.c:(.text+0x67c): multiple definition of `breakinst'
kernel/sysctl.o:sysctl.c:(.text+0x1350): first defined here
kernel/sched/built-in.o: In function `arch_breakpoint':
(.text+0x3b0): multiple definition of `arch_breakpoint'
kernel/sysctl.o:sysctl.c:(.text+0x134c): first defined here
kernel/sched/built-in.o: In function `arch_breakpoint':
(.text+0x3b4): multiple definition of `breakinst'
kernel/sysctl.o:sysctl.c:(.text+0x1350): first defined here
kernel/kprobes.o: In function `arch_breakpoint':
kprobes.c:(.text+0x1690): multiple definition of `arch_breakpoint'
kernel/sysctl.o:sysctl.c:(.text+0x134c): first defined here
kernel/kprobes.o: In function `arch_breakpoint':
kprobes.c:(.text+0x1694): multiple definition of `breakinst'
kernel/sysctl.o:sysctl.c:(.text+0x1350): first defined here
---
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: 18092 bytes --]
next prev parent reply other threads:[~2016-01-28 21:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 19:47 Jeffrey Merkey
2016-01-28 21:41 ` kbuild test robot [this message]
2016-02-01 12:26 ` Maciej W. Rozycki
2016-02-01 16:03 ` Jeff Merkey
2016-02-01 21:25 ` Ralf Baechle
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=201601290507.6eVJpNrW%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=james.hogan@imgtec.com \
--cc=jeffmerkey@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux.mdb@gmail.com \
--cc=ralf@linux-mips.org \
/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®