From: kbuild test robot <lkp@intel.com>
To: Josef Bacik <jbacik@fb.com>
Cc: kbuild-all@01.org, ast@fb.com, tgraf@suug.ch,
daniel@iogearbox.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH] Bpf: allow access into map value arrays
Date: Tue, 30 Aug 2016 22:36:25 +0800 [thread overview]
Message-ID: <201608302256.JtMIhUVA%fengguang.wu@intel.com> (raw)
In-Reply-To: <1472563604-8548-1-git-send-email-jbacik@fb.com>
[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]
Hi Josef,
[auto build test ERROR on v4.8-rc2]
[also build test ERROR on next-20160825]
[cannot apply to linus/master linux/master v4.8-rc4 v4.8-rc3]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
[Suggest to use git(>=2.9.0) format-patch --base=<commit> (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on]
[Check https://git-scm.com/docs/git-format-patch for more information]
url: https://github.com/0day-ci/linux/commits/Josef-Bacik/Bpf-allow-access-into-map-value-arrays/20160830-213112
config: i386-randconfig-i1-201635 (attached as .config)
compiler: gcc-4.8 (Debian 4.8.4-1) 4.8.4
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
kernel/built-in.o: In function `check_alu_op':
>> verifier.c:(.text+0x8efed): undefined reference to `__udivdi3'
verifier.c:(.text+0x8f035): undefined reference to `__udivdi3'
---
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: 24943 bytes --]
prev parent reply other threads:[~2016-08-30 14:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 13:26 Josef Bacik
2016-08-30 14:36 ` 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=201608302256.JtMIhUVA%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=jbacik@fb.com \
--cc=kbuild-all@01.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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®