From: kbuild test robot <lkp@intel.com>
To: Raghu Vatsavayi <rvatsavayi@caviumnetworks.com>
Cc: kbuild-all@01.org, davem@davemloft.net, netdev@vger.kernel.org,
Raghu Vatsavayi <rvatsavayi@caviumnetworks.com>,
Raghu Vatsavayi <raghu.vatsavayi@caviumnetworks.com>,
Derek Chickles <derek.chickles@caviumnetworks.com>,
Satanand Burla <satananda.burla@caviumnetworks.com>,
Felix Manlunas <felix.manlunas@caviumnetworks.com>
Subject: Re: [PATCH net-next V4 2/9] liquidio CN23XX: sysfs VF config support
Date: Sat, 5 Nov 2016 03:53:21 +0800 [thread overview]
Message-ID: <201611050354.uIPrecCP%fengguang.wu@intel.com> (raw)
In-Reply-To: <1478208918-8330-3-git-send-email-rvatsavayi@caviumnetworks.com>
[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]
Hi Raghu,
[auto build test ERROR on net-next/master]
url: https://github.com/0day-ci/linux/commits/Raghu-Vatsavayi/liquidio-CN23XX-VF-support/20161104-054117
config: x86_64-randconfig-s2-11041915 (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/ethernet/cavium/liquidio/lio_main.c: In function 'octeon_enable_sriov':
>> drivers/net/ethernet/cavium/liquidio/lio_main.c:4025: error: 'struct pci_dev' has no member named 'physfn'
vim +4025 drivers/net/ethernet/cavium/liquidio/lio_main.c
4019 */
4020 u = 0;
4021 vfdev = pci_get_device(PCI_VENDOR_ID_CAVIUM,
4022 OCTEON_CN23XX_VF_VID, NULL);
4023 while (vfdev) {
4024 if (vfdev->is_virtfn &&
> 4025 (vfdev->physfn == oct->pci_dev)) {
4026 oct->sriov_info.dpiring_to_vfpcidev_lut[u] =
4027 vfdev;
4028 u += oct->sriov_info.rings_per_vf;
---
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: 29371 bytes --]
next prev parent reply other threads:[~2016-11-04 11:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 21:35 [PATCH net-next V4 0/9] liquidio CN23XX VF support Raghu Vatsavayi
2016-11-03 21:35 ` [PATCH net-next V4 1/9] liquidio CN23XX: HW config for " Raghu Vatsavayi
2016-11-03 21:35 ` [PATCH net-next V4 2/9] liquidio CN23XX: sysfs VF config support Raghu Vatsavayi
2016-11-04 19:53 ` kbuild test robot [this message]
2016-11-03 21:35 ` [PATCH net-next V4 3/9] liquidio CN23XX: Mailbox support Raghu Vatsavayi
2016-11-03 21:35 ` [PATCH net-next V4 4/9] liquidio CN23XX: mailbox interrupt processing Raghu Vatsavayi
2016-11-03 21:35 ` [PATCH net-next V4 5/9] liquidio CN23XX: VF related operations Raghu Vatsavayi
2016-11-03 21:35 ` [PATCH net-next V4 6/9] liquidio CN23XX: device states Raghu Vatsavayi
2016-11-03 21:35 ` [PATCH net-next V4 7/9] liquidio CN23XX: code cleanup Raghu Vatsavayi
2016-11-03 21:35 ` [PATCH net-next V4 8/9] liquidio CN23XX: copyrights changes and alignment Raghu Vatsavayi
2016-11-03 21:35 ` [PATCH net-next V4 9/9] liquidio CN23XX: fix for new check patch errors Raghu Vatsavayi
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=201611050354.uIPrecCP%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=derek.chickles@caviumnetworks.com \
--cc=felix.manlunas@caviumnetworks.com \
--cc=kbuild-all@01.org \
--cc=netdev@vger.kernel.org \
--cc=raghu.vatsavayi@caviumnetworks.com \
--cc=rvatsavayi@caviumnetworks.com \
--cc=satananda.burla@caviumnetworks.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).