netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Jingju Hou <houjingj@marvell.com>
Cc: kbuild-all@01.org, davem@davemloft.net,
	thomas.petazzoni@free-electrons.com, netdev@vger.kernel.org,
	Jingju Hou <houjingj@marvell.com>
Subject: Re: [PATCH] net: mvneta: implement .set_wol and .get_wol
Date: Sun, 22 Jan 2017 19:13:58 +0800	[thread overview]
Message-ID: <201701221945.TgZOYvQL%fengguang.wu@intel.com> (raw)
In-Reply-To: <1485079590-6392-1-git-send-email-houjingj@marvell.com>

[-- Attachment #1: Type: text/plain, Size: 2693 bytes --]

Hi Jingju,

[auto build test ERROR on net-next/master]
[also build test ERROR on v4.10-rc4 next-20170120]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Jingju-Hou/net-mvneta-implement-set_wol-and-get_wol/20170122-181651
config: xtensa-allmodconfig (attached as .config)
compiler: xtensa-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=xtensa 

All error/warnings (new ones prefixed by >>):

   drivers/net/ethernet/marvell/mvneta.c: In function 'mvneta_ethtool_get_wol':
>> drivers/net/ethernet/marvell/mvneta.c:3940:8: error: 'struct mvneta_port' has no member named 'phy_dev'
     if (pp->phy_dev)
           ^
   drivers/net/ethernet/marvell/mvneta.c:3941:32: error: 'struct mvneta_port' has no member named 'phy_dev'
      return phy_ethtool_get_wol(pp->phy_dev, wol);
                                   ^
>> drivers/net/ethernet/marvell/mvneta.c:3941:3: warning: 'return' with a value, in function returning void
      return phy_ethtool_get_wol(pp->phy_dev, wol);
      ^
   drivers/net/ethernet/marvell/mvneta.c: In function 'mvneta_ethtool_set_wol':
   drivers/net/ethernet/marvell/mvneta.c:3949:9: error: 'struct mvneta_port' has no member named 'phy_dev'
     if (!pp->phy_dev)
            ^
   drivers/net/ethernet/marvell/mvneta.c:3952:31: error: 'struct mvneta_port' has no member named 'phy_dev'
     return phy_ethtool_set_wol(pp->phy_dev, wol);
                                  ^
>> drivers/net/ethernet/marvell/mvneta.c:3953:1: warning: control reaches end of non-void function [-Wreturn-type]
    }
    ^

vim +3940 drivers/net/ethernet/marvell/mvneta.c

  3934	{
  3935		struct mvneta_port *pp = netdev_priv(dev);
  3936	
  3937		wol->supported = 0;
  3938		wol->wolopts = 0;
  3939	
> 3940		if (pp->phy_dev)
> 3941			return phy_ethtool_get_wol(pp->phy_dev, wol);
  3942	}
  3943	
  3944	static int
  3945	mvneta_ethtool_set_wol(struct net_device *dev, struct ethtool_wolinfo *wol)
  3946	{
  3947		struct mvneta_port *pp = netdev_priv(dev);
  3948	
> 3949		if (!pp->phy_dev)
  3950			return -EOPNOTSUPP;
  3951	
  3952		return phy_ethtool_set_wol(pp->phy_dev, wol);
> 3953	}
  3954	
  3955	static const struct net_device_ops mvneta_netdev_ops = {
  3956		.ndo_open            = mvneta_open,

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

  reply	other threads:[~2017-01-22 11:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-22 10:06 [PATCH] net: mvneta: implement .set_wol and .get_wol Jingju Hou
2017-01-22 11:13 ` kbuild test robot [this message]
2017-01-22 11:21 ` kbuild test robot
2017-01-22 16:49 ` Andrew Lunn
  -- strict thread matches above, loose matches on Subject: below --
2017-01-23  2:43 Jingju Hou
2017-01-23  2:58 ` Jisheng Zhang

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=201701221945.TgZOYvQL%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=davem@davemloft.net \
    --cc=houjingj@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).