Netdev List
 help / color / mirror / Atom feed
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] net: dummy: Introduce dummy virtual functions
Date: Sat, 12 Nov 2016 03:23:06 +0800	[thread overview]
Message-ID: <201611120301.6TsVFKEp%fengguang.wu@intel.com> (raw)
In-Reply-To: <20161111173333.12603-1-phil@nwl.cc>

[-- Attachment #1: Type: text/plain, Size: 1628 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/20161112-013558
config: m68k-sun3_defconfig (attached as .config)
compiler: m68k-linux-gcc (GCC) 4.9.0
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=m68k 

All errors (new ones prefixed by >>):

   drivers/net/dummy.c:53:2: error: unknown field 'sriov' specified in initializer
     .sriov = &pdev_sriov,
     ^
   drivers/net/dummy.c:53:2: warning: initialization makes integer from pointer without a cast
   drivers/net/dummy.c:53:2: warning: (near initialization for 'pci_pdev.is_virtfn')
   drivers/net/dummy.c:53:2: error: initializer element is not computable at load time
   drivers/net/dummy.c:53:2: error: (near initialization for 'pci_pdev.is_virtfn')
>> drivers/net/dummy.c:54:14: error: 'pci_bus_type' undeclared here (not in a function)
     .dev.bus = &pci_bus_type,
                 ^

vim +/pci_bus_type +54 drivers/net/dummy.c

    47	static int num_vfs;
    48	
    49	static struct pci_sriov pdev_sriov;
    50	
    51	static struct pci_dev pci_pdev = {
    52		.is_physfn = 1,
  > 53		.sriov = &pdev_sriov,
  > 54		.dev.bus = &pci_bus_type,
    55	};
    56	
    57	struct vf_data_storage {

---
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: 11553 bytes --]

  reply	other threads:[~2016-11-11 19:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-11 17:33 [net-next PATCH] net: dummy: Introduce dummy virtual functions Phil Sutter
2016-11-11 19:23 ` kbuild test robot [this message]
2016-11-11 19:23 ` kbuild test robot

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=201611120301.6TsVFKEp%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