From: kbuild test robot <lkp@intel.com>
To: Zefir Kurtisi <zefir.kurtisi@neratec.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org, f.fainelli@gmail.com,
andrew@lunn.ch
Subject: Re: [PATCH] phy state machine: failsafe leave invalid RUNNING state
Date: Thu, 5 Jan 2017 04:23:52 +0800 [thread overview]
Message-ID: <201701050413.aRmqu7mJ%fengguang.wu@intel.com> (raw)
In-Reply-To: <1483542298-9747-1-git-send-email-zefir.kurtisi@neratec.com>
[-- Attachment #1: Type: text/plain, Size: 1404 bytes --]
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
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 29567 bytes --]
next prev parent reply other threads:[~2017-01-04 20:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 15:04 [PATCH] phy state machine: failsafe leave invalid RUNNING state Zefir Kurtisi
2017-01-04 15:13 ` Florian Fainelli
2017-01-04 15:27 ` Zefir Kurtisi
2017-01-04 15:30 ` Florian Fainelli
2017-01-04 16:10 ` Zefir Kurtisi
2017-01-04 16:16 ` Andrew Lunn
2017-01-04 16:24 ` [SIDE DISCUSSION] " Matthias May
2017-01-04 21:44 ` Florian Fainelli
2017-01-05 9:23 ` Zefir Kurtisi
2017-01-05 19:39 ` Florian Fainelli
2017-01-04 20:07 ` kbuild test robot
2017-01-04 20:23 ` kbuild test robot [this message]
2017-01-06 11:14 ` [PATCH v2] " Zefir Kurtisi
2017-01-08 23:16 ` David Miller
2017-01-09 1:24 ` Florian Fainelli
2017-01-09 20:38 ` 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=201701050413.aRmqu7mJ%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=kbuild-all@01.org \
--cc=netdev@vger.kernel.org \
--cc=zefir.kurtisi@neratec.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).