From: kbuild test robot <lkp@intel.com>
To: Phil Sutter <phil@nwl.cc>
Cc: kbuild-all@01.org, David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, Sabrina Dubroca <sd@queasysnail.net>
Subject: Re: [net-next PATCH v4] net: dummy: Introduce dummy virtual functions
Date: Thu, 24 Nov 2016 16:25:11 +0800 [thread overview]
Message-ID: <201611241608.SkL20sAj%fengguang.wu@intel.com> (raw)
In-Reply-To: <20161123162539.7778-1-phil@nwl.cc>
[-- Attachment #1: Type: text/plain, Size: 1282 bytes --]
Hi Phil,
[auto build test ERROR on net-next/master]
url: https://github.com/0day-ci/linux/commits/Phil-Sutter/net-dummy-Introduce-dummy-virtual-functions/20161124-040435
config: x86_64-randconfig-a0-11241529 (attached as .config)
compiler: gcc-4.4 (Debian 4.4.7-8) 4.4.7
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
>> drivers/net/dummy.c:54: error: unknown field 'sriov' specified in initializer
drivers/net/dummy.c:54: warning: initialization makes integer from pointer without a cast
>> drivers/net/dummy.c:54: error: initializer element is not computable at load time
drivers/net/dummy.c:54: error: (near initialization for 'pci_pdev.is_virtfn')
cc1: warning: unrecognized command line option "-Wno-maybe-uninitialized"
vim +/sriov +54 drivers/net/dummy.c
48
49 static struct pci_sriov pdev_sriov;
50
51 static struct pci_dev pci_pdev = {
52 .is_physfn = 0,
53 #ifdef CONFIG_PCI_ATS
> 54 .sriov = &pdev_sriov,
55 #endif
56 #ifdef CONFIG_PCI
57 .dev.bus = &pci_bus_type,
---
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: 32096 bytes --]
prev parent reply other threads:[~2016-11-24 8:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 16:25 [net-next PATCH v4] net: dummy: Introduce dummy virtual functions Phil Sutter
2016-11-24 8:25 ` 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=201611241608.SkL20sAj%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=kbuild-all@01.org \
--cc=netdev@vger.kernel.org \
--cc=phil@nwl.cc \
--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