[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210623233854.03ed9240@thinkpad>
Date: Wed, 23 Jun 2021 23:38:54 +0200
From: Marek Behun <marek.behun@....cz>
To: Ling Pei Lee <pei.lee.ling@...el.com>
Cc: Russell King <linux@...linux.org.uk>, Andrew Lunn <andrew@...n.ch>,
Heiner Kallweit <hkallweit1@...il.com>, davem@...emloft.net,
Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, weifeng.voon@...el.com,
vee.khee.wong@...ux.intel.com, vee.khee.wong@...el.com
Subject: Re: [PATCH net-next] net: phy: marvell10g: enable WoL for mv2110
On Wed, 23 Jun 2021 21:09:29 +0800
Ling Pei Lee <pei.lee.ling@...el.com> wrote:
> + /* Enable the WOL interrupt */
> + ret = phy_set_bits_mmd(phydev, MDIO_MMD_VEND2,
> + MV_V2_PORT_INTR_MASK,
> + MV_V2_WOL_INTR_EN);
> +
> + if (ret < 0)
> + return ret;
Hi, in addition to what Russell said, please remove the extra newline
between function call and return value check, i.e. instead of
ret = phy_xyz(...);
if (ret)
return ret;
ret = phy_xyz(...);
if (ret)
return ret;
do
ret = phy_xyz(...);
if (ret)
return ret;
ret = phy_xyz(...);
if (ret)
return ret;
This is how this driver does this everywhere else.
Do you have a device that uses this WoL feature?
Marek
Powered by blists - more mailing lists