From: kbuild test robot <fengguang.wu@intel.com>
To: Ganesh Goudar <ganeshgr@chelsio.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org
Subject: [net-next:master 177/195] drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c:4646: warning: unused variable 'port_vec'
Date: Fri, 20 Jan 2017 04:17:06 +0800 [thread overview]
Message-ID: <201701200402.eeWuIlxm%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2286 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master
head: 4567d686f5c6d955e57a3afa1741944c1e7f4033
commit: 96fe11f27b70f6b64f62a2d13ed209aa02e02a48 [177/195] cxgb4: Implement ndo_get_phys_port_id for mgmt dev
config: x86_64-randconfig-a0-01200234 (attached as .config)
compiler: gcc-4.4 (Debian 4.4.7-8) 4.4.7
reproduce:
git checkout 96fe11f27b70f6b64f62a2d13ed209aa02e02a48
# save the attached .config to linux build tree
make ARCH=x86_64
All warnings (new ones prefixed by >>):
drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c: In function 'init_one':
>> drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c:4646: warning: unused variable 'port_vec'
>> drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c:4646: warning: unused variable 'v'
drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c: In function 'cxgb_select_queue':
drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c:923: warning: 'vlan_tci' may be used uninitialized in this function
At top level:
cc1: warning: unrecognized command line option "-Wno-maybe-uninitialized"
drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.o: warning: objtool: __skb_put()+0x65: function has unreachable instruction
vim +/port_vec +4646 drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c
4630 fill_vf_station_mac_addr(adap);
4631 return num_vfs;
4632 }
4633 #endif
4634
4635 static int init_one(struct pci_dev *pdev, const struct pci_device_id *ent)
4636 {
4637 int func, i, err, s_qpp, qpp, num_seg;
4638 struct port_info *pi;
4639 bool highdma = false;
4640 struct adapter *adapter = NULL;
4641 struct net_device *netdev;
4642 void __iomem *regs;
4643 u32 whoami, pl_rev;
4644 enum chip_type chip;
4645 static int adap_idx = 1;
> 4646 u32 v, port_vec;
4647
4648 printk_once(KERN_INFO "%s - version %s\n", DRV_DESC, DRV_VERSION);
4649
4650 err = pci_request_regions(pdev, KBUILD_MODNAME);
4651 if (err) {
4652 /* Just info, some other driver may have claimed the device. */
4653 dev_info(&pdev->dev, "cannot obtain PCI resources\n");
4654 return err;
---
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: 34801 bytes --]
reply other threads:[~2017-01-19 20:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201701200402.eeWuIlxm%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=ganeshgr@chelsio.com \
--cc=kbuild-all@01.org \
--cc=netdev@vger.kernel.org \
/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