From: kbuild test robot <lkp@intel.com>
To: Jingju Hou <houjingj@marvell.com>
Cc: kbuild-all@01.org, davem@davemloft.net, jszhang@marvell.com,
thomas.petazzoni@free-electrons.com, netdev@vger.kernel.org,
Jingju Hou <houjingj@marvell.com>
Subject: Re: [PATCHv2 net-next] net: mvneta: implement .set_wol and .get_wol
Date: Mon, 23 Jan 2017 12:02:27 +0800 [thread overview]
Message-ID: <201701231121.mUDWb17U%fengguang.wu@intel.com> (raw)
In-Reply-To: <1485139447-11067-1-git-send-email-houjingj@marvell.com>
[-- Attachment #1: Type: text/plain, Size: 2471 bytes --]
Hi Jingju,
[auto build test ERROR on net-next/master]
url: https://github.com/0day-ci/linux/commits/Jingju-Hou/net-mvneta-implement-set_wol-and-get_wol/20170123-105218
config: ia64-allmodconfig (attached as .config)
compiler: ia64-linux-gcc (GCC) 6.2.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=ia64
All errors (new ones prefixed by >>):
drivers/net/ethernet/marvell/mvneta.c: In function 'mvneta_ethtool_get_wol':
>> drivers/net/ethernet/marvell/mvneta.c:3938:9: error: 'struct net_device' has no member named 'phy_dev'; did you mean 'phydev'?
if (dev->phy_dev)
^~
drivers/net/ethernet/marvell/mvneta.c:3939:33: error: 'struct net_device' has no member named 'phy_dev'; did you mean 'phydev'?
return phy_ethtool_get_wol(dev->phy_dev, wol);
^~
drivers/net/ethernet/marvell/mvneta.c:3939:10: warning: 'return' with a value, in function returning void
return phy_ethtool_get_wol(dev->phy_dev, wol);
^~~~~~~~~~~~~~~~~~~
drivers/net/ethernet/marvell/mvneta.c:3933:1: note: declared here
mvneta_ethtool_get_wol(struct net_device *dev, struct ethtool_wolinfo *wol)
^~~~~~~~~~~~~~~~~~~~~~
drivers/net/ethernet/marvell/mvneta.c: In function 'mvneta_ethtool_set_wol':
drivers/net/ethernet/marvell/mvneta.c:3945:10: error: 'struct net_device' has no member named 'phy_dev'; did you mean 'phydev'?
if (!dev->phy_dev)
^~
drivers/net/ethernet/marvell/mvneta.c:3948:32: error: 'struct net_device' has no member named 'phy_dev'; did you mean 'phydev'?
return phy_ethtool_set_wol(dev->phy_dev, wol);
^~
drivers/net/ethernet/marvell/mvneta.c:3949:1: warning: control reaches end of non-void function [-Wreturn-type]
}
^
vim +3938 drivers/net/ethernet/marvell/mvneta.c
3932 static void
3933 mvneta_ethtool_get_wol(struct net_device *dev, struct ethtool_wolinfo *wol)
3934 {
3935 wol->supported = 0;
3936 wol->wolopts = 0;
3937
> 3938 if (dev->phy_dev)
3939 return phy_ethtool_get_wol(dev->phy_dev, wol);
3940 }
3941
---
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: 45821 bytes --]
next prev parent reply other threads:[~2017-01-23 4:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 2:44 [PATCHv2 net-next] net: mvneta: implement .set_wol and .get_wol Jingju Hou
2017-01-23 2:52 ` Jisheng Zhang
2017-01-23 4:02 ` kbuild test robot [this message]
2017-01-23 4:04 ` kbuild test robot
2017-01-23 4:27 ` David Miller
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=201701231121.mUDWb17U%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=houjingj@marvell.com \
--cc=jszhang@marvell.com \
--cc=kbuild-all@01.org \
--cc=netdev@vger.kernel.org \
--cc=thomas.petazzoni@free-electrons.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).