From: David Miller <davem@davemloft.net>
To: rmk+kernel@armlinux.org.uk
Cc: andrew@lunn.ch, f.fainelli@gmail.com, hkallweit1@gmail.com,
netdev@vger.kernel.org
Subject: Re: [PATCH] net: phy: marvell10g: allow PHY to probe without firmware
Date: Wed, 05 Jun 2019 18:48:27 -0700 (PDT) [thread overview]
Message-ID: <20190605.184827.1552392791102735448.davem@davemloft.net> (raw)
In-Reply-To: <E1hYTO0-0000MZ-2d@rmk-PC.armlinux.org.uk>
From: Russell King <rmk+kernel@armlinux.org.uk>
Date: Wed, 05 Jun 2019 11:43:16 +0100
> + (state == PHY_UP || state == PHY_RESUMING)) {
drivers/net/phy/marvell10g.c: In function ‘mv3310_link_change_notify’:
drivers/net/phy/marvell10g.c:268:35: error: ‘PHY_RESUMING’ undeclared (first use in this function); did you mean ‘RPM_RESUMING’?
(state == PHY_UP || state == PHY_RESUMING)) {
^~~~~~~~~~~~
RPM_RESUMING
drivers/net/phy/marvell10g.c:268:35: note: each undeclared identifier is reported only once for each function it appears in
At top level:
drivers/net/phy/marvell10g.c:262:13: warning: ‘mv3310_link_change_notify’ defined but not used [-Wunused-function]
static void mv3310_link_change_notify(struct phy_device *phydev)
^~~~~~~~~~~~~~~~~~~~~~~~~
next prev parent reply other threads:[~2019-06-06 1:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 10:43 [PATCH] net: phy: marvell10g: allow PHY to probe without firmware Russell King
2019-06-05 12:37 ` Andrew Lunn
2019-06-06 1:48 ` David Miller [this message]
2019-06-06 7:59 ` Russell King - ARM Linux admin
2019-06-06 12:31 ` Andrew Lunn
2019-06-06 12:42 ` Andrew Lunn
2019-06-06 18:24 ` Heiner Kallweit
2019-06-06 18:36 ` Andrew Lunn
2019-06-06 21:37 ` Russell King - ARM Linux admin
2019-06-10 13:40 ` Heiner Kallweit
2019-06-10 14:13 ` Russell King - ARM Linux admin
2019-06-06 21:16 ` Russell King - ARM Linux admin
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=20190605.184827.1552392791102735448.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
/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).