From: kbuild test robot <lkp@intel.com>
To: wei.guo.simon@gmail.com
Cc: kbuild-all@01.org, mpe@ellerman.id.au,
Simon Guo <wei.guo.simon@gmail.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Kees Cook <keescook@chromium.org>,
Rashmica Gupta <rashmicy@gmail.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Laurent Dufour <ldufour@linux.vnet.ibm.com>
Subject: Re: [PATCH v3] powerpc: Export thread_struct.used_vr/used_vsr to user space
Date: Thu, 7 Jul 2016 12:27:55 +0800 [thread overview]
Message-ID: <201607071209.cl4WjTxD%fengguang.wu@intel.com> (raw)
In-Reply-To: <1467858449-3406-1-git-send-email-wei.guo.simon@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]
Hi,
[auto build test ERROR on powerpc/next]
[also build test ERROR on v4.7-rc6 next-20160706]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/wei-guo-simon-gmail-com/powerpc-Export-thread_struct-used_vr-used_vsr-to-user-space/20160707-103044
base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next
config: powerpc-defconfig (attached as .config)
compiler: powerpc-linux-gnu-gcc (Debian 5.3.1-8) 5.3.1 20160205
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=powerpc
All errors (new ones prefixed by >>):
arch/powerpc/kernel/built-in.o: In function `arch_ptrace':
>> (.text+0xad4): undefined reference to `__get_user_bad'
---
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: 7772 bytes --]
prev parent reply other threads:[~2016-07-07 4:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 2:27 wei.guo.simon
2016-07-07 4:27 ` kbuild test robot [this message]
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=201607071209.cl4WjTxD%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=benh@kernel.crashing.org \
--cc=kbuild-all@01.org \
--cc=keescook@chromium.org \
--cc=ldufour@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=rashmicy@gmail.com \
--cc=wei.guo.simon@gmail.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®