netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"peppe.cavallaro@st.com" <peppe.cavallaro@st.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH v3] stmmac: fix check for phydev being open
Date: Tue, 8 Sep 2015 22:53:51 +0300	[thread overview]
Message-ID: <55EF3CCF.4000608@cogentembedded.com> (raw)
In-Reply-To: <1441716387.21150.0.camel@synopsys.com>

Hello.

On 09/08/2015 03:46 PM, Alexey Brodkin wrote:

>>> Current check of phydev with IS_ERR(phydev) may make not much sense
>>> because of_phy_connect() returns NULL on failure instead of error value.
>>>
>>> Still for checking result of phy_connect() IS_ERR() makes perfect sense.
>>>
>>> So let's use combined check IS_ERR_OR_NULL() that covers both cases.
>>>
>>> Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>>> Cc: Giuseppe Cavallaro <peppe.cavallaro@st.com>
>>> Cc: linux-kernel@vger.kernel.org
>>> Cc: stable@vger.kernel.org
>>> Cc: David Miller <davem@davemloft.net>
>>> Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
>>> ---
>>>
>>> Changes compared to v2:
>>>    * Updated commit message with mention of of_phy_connect() instead of
>>>      of_phy_attach().
>>>    * Return ENODEV in case of of_phy_connect() failure
>>>
>>> Changes compared to v1:
>>>    * Use IS_ERR_OR_NULL() instead of discrete checks for null and err
>>>
>>>    drivers/net/ethernet/stmicro/stmmac/stmmac_main.c | 7 +++++--
>>>    1 file changed, 5 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
>>> index 864b476..e2c9c86 100644
>>> --- a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
>>> +++ b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
>>> @@ -837,9 +837,12 @@ static int stmmac_init_phy(struct net_device *dev)
>>>    				     interface);
>>>    	}
>>>
>>> -	if (IS_ERR(phydev)) {
>>> +	if (IS_ERR_OR_NULL(phydev)) {
>>>    		pr_err("%s: Could not attach to PHY\n", dev->name);
>>> -		return PTR_ERR(phydev);
>>> +		if (!phydev)
>>> +			return -ENODEV;
>>> +		else
>>> +			return PTR_ERR(phydev);
>>
>>      Don't need *else* after *return* and scripts/checkpatch.pl should have
>> complained about that.
>
> ./scripts/checkpatch.pl 0001-stmmac-fix-check-for-phydev-being-open.patch
> total: 0 errors, 0 warnings, 0 checks, 14 lines checked

    Hm... I bet I saw such warning from checkpatch.pl recently (it was a false 
positive though, so maybe the check was removed recently, not sure). Your 
patch is clean indeed, however my comment is still valid.

> -Alexey

MBR, Sergei

  reply	other threads:[~2015-09-08 19:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-08  8:43 [PATCH v3] stmmac: fix check for phydev being open Alexey Brodkin
2015-09-08 11:20 ` Sergei Shtylyov
2015-09-08 12:46   ` Alexey Brodkin
2015-09-08 19:53     ` Sergei Shtylyov [this message]
2015-09-09 14:44       ` Alexey Brodkin

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=55EF3CCF.4000608@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=Alexey.Brodkin@synopsys.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=peppe.cavallaro@st.com \
    --cc=stable@vger.kernel.org \
    /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).