From: kbuild test robot <lkp@intel.com>
To: Martijn Coenen <maco@google.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: drivers/android/.tmp_gl_binder.o:undefined reference to `__user_bad'
Date: Mon, 2 Jul 2018 12:52:36 +0800 [thread overview]
Message-ID: <201807021228.PZ5wzCyl%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1426 bytes --]
Hi Martijn,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 021c91791a5e7e85c567452f1be3e4c2c6cb6063
commit: 1190b4e38f97023154e6b3bef61b251aa5f970d0 ANDROID: binder: remove 32-bit binder interface.
date: 7 weeks ago
config: microblaze-allmodconfig (attached as .config)
compiler: microblaze-linux-gcc (GCC) 8.1.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 1190b4e38f97023154e6b3bef61b251aa5f970d0
# save the attached .config to linux build tree
GCC_VERSION=8.1.0 make.cross ARCH=microblaze
All errors (new ones prefixed by >>):
drivers/android/binder.o: In function `binder_thread_write':
>> drivers/android/.tmp_gl_binder.o:(.text+0xcbb0): undefined reference to `__user_bad'
drivers/android/.tmp_gl_binder.o:(.text+0xcbdc): undefined reference to `__user_bad'
drivers/android/.tmp_gl_binder.o:(.text+0xcfc4): undefined reference to `__user_bad'
drivers/android/.tmp_gl_binder.o:(.text+0xd650): undefined reference to `__user_bad'
drivers/android/.tmp_gl_binder.o:(.text+0xdbc8): undefined reference to `__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/gzip, Size: 52302 bytes --]
next reply other threads:[~2018-07-02 4:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 4:52 kbuild test robot [this message]
2018-07-02 9:27 ` Martijn Coenen
2018-08-06 3:41 kbuild test robot
2018-08-11 9:22 kbuild test robot
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=201807021228.PZ5wzCyl%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@google.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®