From: David Miller <davem@davemloft.net>
To: houjingj@marvell.com
Cc: jszhang@marvell.com, thomas.petazzoni@free-electrons.com,
netdev@vger.kernel.org
Subject: Re: [PATCH v3 net-next] net: mvneta: implement .set_wol and .get_wol
Date: Sun, 22 Jan 2017 23:29:36 -0500 (EST) [thread overview]
Message-ID: <20170122.232936.1713221615026642410.davem@davemloft.net> (raw)
In-Reply-To: <1485144678-11777-1-git-send-email-houjingj@marvell.com>
From: Jingju Hou <houjingj@marvell.com>
Date: Mon, 23 Jan 2017 12:11:18 +0800
> The mvneta itself does not support WOL, but the PHY might.
> So pass the calls to the PHY
>
> Signed-off-by: Jingju Hou <houjingj@marvell.com>
> ---
> Since v2:
> - it should be phydev member not phy_dev
>
> drivers/net/ethernet/marvell/mvneta.c | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
> diff --git a/drivers/net/ethernet/marvell/mvneta.c b/drivers/net/ethernet/marvell/mvneta.c
> index e05e227..fea4968 100644
> --- a/drivers/net/ethernet/marvell/mvneta.c
> +++ b/drivers/net/ethernet/marvell/mvneta.c
> @@ -3908,6 +3908,25 @@ static int mvneta_ethtool_get_rxfh(struct net_device *dev, u32 *indir, u8 *key,
> return 0;
> }
>
> +static void
> +mvneta_ethtool_get_wol(struct net_device *dev, struct ethtool_wolinfo *wol)
> +{
> + wol->supported = 0;
> + wol->wolopts = 0;
> +
> + if (dev->phy_dev)
You are not testing the build of this patch, you are still using
phy_dev here. Either that or your commit message is not accurate.
Either way this patch or it's commit message is wrong.
I think you need to stop, take a deep breath, and take your time
fixing this.
Right now you are spitting out a new patch just minutes after
a previous submission, and these patches still have the same
bugs.
next prev parent reply other threads:[~2017-01-23 4:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 4:11 [PATCH v3 net-next] net: mvneta: implement .set_wol and .get_wol Jingju Hou
2017-01-23 4:29 ` David Miller [this message]
2017-01-23 4:55 ` YUAN Linyu
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=20170122.232936.1713221615026642410.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=houjingj@marvell.com \
--cc=jszhang@marvell.com \
--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