From: kbuild test robot <lkp@intel.com>
To: Xin Long <lucien.xin@gmail.com>
Cc: kbuild-all@01.org, network dev <netdev@vger.kernel.org>,
davem@davemloft.net,
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
Sabrina Dubroca <sd@queasysnail.net>
Subject: Re: [PATCH net] sock_diag: request _diag module only when the family or proto has been registered
Date: Wed, 18 Oct 2017 16:33:17 +0800 [thread overview]
Message-ID: <201710181603.1FtB2FUI%fengguang.wu@intel.com> (raw)
In-Reply-To: <69c0824505548e733f2f7be3ff288f2c4e461afa.1508217236.git.lucien.xin@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 731 bytes --]
Hi Xin,
[auto build test ERROR on net/master]
url: https://github.com/0day-ci/linux/commits/Xin-Long/sock_diag-request-_diag-module-only-when-the-family-or-proto-has-been-registered/20171018-152434
config: i386-randconfig-a0-201742 (attached as .config)
compiler: gcc-5 (Debian 5.4.1-2) 5.4.1 20160904
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
net/core/sock_diag.o: In function `sock_diag_request_module':
>> sock_diag.c:(.text+0x5a5): undefined reference to `inet_protos'
---
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: 24738 bytes --]
next prev parent reply other threads:[~2017-10-18 8:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 5:13 [PATCH net] sock_diag: request _diag module only when the family or proto has been registered Xin Long
2017-10-17 11:16 ` Eric Dumazet
2017-10-17 11:24 ` Eric Dumazet
2017-10-17 11:35 ` Eric Dumazet
2017-10-17 11:39 ` Marcelo Ricardo Leitner
2017-10-18 8:33 ` kbuild test robot [this message]
2017-10-18 9:38 ` kbuild test robot
2017-10-18 13:33 ` Xin Long
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=201710181603.1FtB2FUI%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=kbuild-all@01.org \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
/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).