From: kbuild test robot <lkp@intel.com>
To: Yuchung Cheng <ycheng@google.com>
Cc: kbuild-all@01.org, davem@davemloft.net, soheil@google.com,
francisyyan@gmail.com, netdev@vger.kernel.org,
ncardwell@google.com, edumazet@google.com,
Yuchung Cheng <ycheng@google.com>
Subject: Re: [PATCH net-next 6/6] tcp: SOF_TIMESTAMPING_OPT_STATS option for SO_TIMESTAMPING
Date: Sun, 27 Nov 2016 10:06:32 +0800 [thread overview]
Message-ID: <201611270949.bI4i0eoG%fengguang.wu@intel.com> (raw)
In-Reply-To: <1480191016-73210-7-git-send-email-ycheng@google.com>
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
Hi Francis,
[auto build test ERROR on net-next/master]
url: https://github.com/0day-ci/linux/commits/Yuchung-Cheng/tcp-sender-chronographs-instrumentation/20161127-041428
config: arm-spear6xx_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 >>):
net/built-in.o: In function `__skb_tstamp_tx':
>> net/core/skbuff.c:3846: undefined reference to `tcp_get_timestamping_opt_stats'
vim +3846 net/core/skbuff.c
3840 return;
3841
3842 if (tsonly) {
3843 if ((sk->sk_tsflags & SOF_TIMESTAMPING_OPT_STATS) &&
3844 sk->sk_protocol == IPPROTO_TCP &&
3845 sk->sk_type == SOCK_STREAM)
> 3846 skb = tcp_get_timestamping_opt_stats(sk);
3847 else
3848 skb = alloc_skb(0, GFP_ATOMIC);
3849 } else {
---
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: 14586 bytes --]
next prev parent reply other threads:[~2016-11-27 2:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-26 20:10 [PATCH net-next 0/6] tcp: sender chronographs instrumentation Yuchung Cheng
2016-11-26 20:10 ` [PATCH net-next 1/6] tcp: instrument tcp sender limits chronographs Yuchung Cheng
2016-11-26 20:10 ` [PATCH net-next 2/6] tcp: instrument how long TCP is busy sending Yuchung Cheng
2016-11-26 20:10 ` [PATCH net-next 3/6] tcp: instrument how long TCP is limited by receive window Yuchung Cheng
2016-11-26 20:10 ` [PATCH net-next 4/6] tcp: instrument how long TCP is limited by insufficient send buffer Yuchung Cheng
2016-11-26 20:10 ` [PATCH net-next 5/6] tcp: export sender limits chronographs to TCP_INFO Yuchung Cheng
2016-11-26 20:10 ` [PATCH net-next 6/6] tcp: SOF_TIMESTAMPING_OPT_STATS option for SO_TIMESTAMPING Yuchung Cheng
2016-11-27 2:06 ` kbuild test robot [this message]
2016-11-28 21:19 ` [PATCH net-next 0/6] tcp: sender chronographs instrumentation David Miller
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=201611270949.bI4i0eoG%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=francisyyan@gmail.com \
--cc=kbuild-all@01.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=soheil@google.com \
--cc=ycheng@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;
as well as URLs for NNTP newsgroup(s).