[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <201701050413.aRmqu7mJ%fengguang.wu@intel.com>
Date: Thu, 5 Jan 2017 04:23:52 +0800
From: kbuild test robot <lkp@...el.com>
To: Zefir Kurtisi <zefir.kurtisi@...atec.com>
Cc: kbuild-all@...org, netdev@...r.kernel.org, f.fainelli@...il.com,
andrew@...n.ch
Subject: Re: [PATCH] phy state machine: failsafe leave invalid RUNNING state
Hi Zefir,
[auto build test ERROR on net-next/master]
[also build test ERROR on v4.10-rc2 next-20170104]
[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/Zefir-Kurtisi/phy-state-machine-failsafe-leave-invalid-RUNNING-state/20170105-033018
config: i386-randconfig-i1-201701 (attached as .config)
compiler: gcc-4.8 (Debian 4.8.4-1) 4.8.4
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
drivers/net/phy/phy.c: In function 'phy_state_machine':
>> drivers/net/phy/phy.c:1075:20: error: 'struct phy_device' has no member named 'dev'
dev_warn(&phydev->dev, "no link in PHY_RUNNING\n");
^
vim +1075 drivers/net/phy/phy.c
1069 * Failsafe: check that nobody set phydev->link=0 between two
1070 * poll cycles, otherwise we won't leave RUNNING state as long
1071 * as link remains down.
1072 */
1073 if (!phydev->link && phydev->state == PHY_RUNNING) {
1074 phydev->state = PHY_CHANGELINK;
> 1075 dev_warn(&phydev->dev, "no link in PHY_RUNNING\n");
1076 }
1077 break;
1078 case PHY_CHANGELINK:
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
Download attachment ".config.gz" of type "application/gzip" (29567 bytes)
Powered by blists - more mailing lists