From: kbuild test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org, dhowells@redhat.com,
linux-afs@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 3/9] rxrpc: Add per-peer RTT tracker
Date: Thu, 22 Sep 2016 12:34:17 +0800 [thread overview]
Message-ID: <201609221209.SODRGcBr%fengguang.wu@intel.com> (raw)
In-Reply-To: <147450476978.14691.9512799255128693593.stgit@warthog.procyon.org.uk>
[-- Attachment #1: Type: text/plain, Size: 808 bytes --]
Hi David,
[auto build test ERROR on net-next/master]
url: https://github.com/0day-ci/linux/commits/David-Howells/rxrpc-Preparation-for-slow-start-algorithm/20160922-085242
config: arm-omap2plus_defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 6.1.1-9) 6.1.1 20160705
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=arm
All errors (new ones prefixed by >>):
>> ERROR: "__aeabi_uldivmod" [net/rxrpc/af-rxrpc.ko] undefined!
---
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: 28256 bytes --]
next prev parent reply other threads:[~2016-09-22 4:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 0:39 [PATCH net-next 0/9] rxrpc: Preparation for slow-start algorithm David Howells
2016-09-22 0:39 ` [PATCH net-next 1/9] rxrpc: Don't store the rxrpc header in the Tx queue sk_buffs David Howells
2016-09-22 0:39 ` [PATCH net-next 2/9] rxrpc: Add re-sent Tx annotation David Howells
2016-09-22 0:39 ` [PATCH net-next 3/9] rxrpc: Add per-peer RTT tracker David Howells
2016-09-22 4:34 ` kbuild test robot [this message]
2016-09-22 4:56 ` kbuild test robot
2016-09-22 0:39 ` [PATCH net-next 4/9] rxrpc: Send pings to get RTT data David Howells
2016-09-22 0:39 ` [PATCH net-next 5/9] rxrpc: Expedite ping response transmission David Howells
2016-09-22 0:39 ` [PATCH net-next 6/9] rxrpc: Add ktime_sub_ms() David Howells
2016-09-22 0:39 ` [PATCH net-next 7/9] rxrpc: Obtain RTT data by requesting ACKs on DATA packets David Howells
2016-09-22 0:40 ` [PATCH net-next 8/9] rxrpc: Reduce the number of PING ACKs sent David Howells
2016-09-22 1:25 ` kbuild test robot
2016-09-22 0:40 ` [PATCH net-next 9/9] rxrpc: Reduce the number of ACK-Requests sent David Howells
2016-09-22 5:24 ` kbuild test robot
2016-09-22 8:10 ` [PATCH net-next 0/9] rxrpc: Preparation for slow-start algorithm David Howells
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=201609221209.SODRGcBr%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=dhowells@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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