From: kbuild test robot <lkp@intel.com>
To: Jeff Merkey <linux.mdb@gmail.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Don Zickus <dzickus@redhat.com>,
Ulrich Obergfell <uobergfe@redhat.com>,
Aaron Tomlin <atomlin@redhat.com>, Michal Hocko <mhocko@suse.cz>,
Frederic Weisbecker <fweisbec@gmail.com>,
Tejun Heo <tj@kernel.org>,
Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com>,
Chris Metcalf <cmetcalf@ezchip.com>
Subject: Re: [PATCH v2] Add hard/soft lockup debugger entry points
Date: Wed, 27 Jan 2016 02:46:25 +0800 [thread overview]
Message-ID: <201601270229.JYXIVXHh%fengguang.wu@intel.com> (raw)
In-Reply-To: <20160126170454.GA28216@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 942 bytes --]
Hi Jeff,
[auto build test ERROR on v4.5-rc1]
[also build test ERROR on next-20160125]
[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/Jeff-Merkey/Add-hard-soft-lockup-debugger-entry-points/20160127-010930
config: sparc64-defconfig (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=sparc64
All errors (new ones prefixed by >>):
kernel/built-in.o: In function `watchdog_timer_fn':
>> watchdog.c:(.text+0x736ec): undefined reference to `arch_kgdb_breakpoint'
---
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: 16661 bytes --]
next prev parent reply other threads:[~2016-01-26 18:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 17:04 Jeff Merkey
2016-01-26 17:22 ` Chris Metcalf
2016-01-26 17:26 ` Jeff Merkey
2016-01-26 17:45 ` kbuild test robot
2016-01-26 18:46 ` kbuild test robot [this message]
2016-01-26 19:33 ` Jeff Merkey
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=201601270229.JYXIVXHh%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=atomlin@redhat.com \
--cc=cmetcalf@ezchip.com \
--cc=dzickus@redhat.com \
--cc=fweisbec@gmail.com \
--cc=hidehiro.kawai.ez@hitachi.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.mdb@gmail.com \
--cc=mhocko@suse.cz \
--cc=tj@kernel.org \
--cc=uobergfe@redhat.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®