From: Dan Carpenter <error27@gmail.com>
To: giulio.benetti@micronovasrl.com
Cc: grant.likely@secretlab.ca, jeremy.kerr@canonical.com,
afleming@freescale.com, jezz@sysmic.org,
devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org, David Miller <davem@davemloft.net>
Subject: Re: [patch] of: check for IS_ERR()
Date: Mon, 29 Mar 2010 18:41:09 +0300 [thread overview]
Message-ID: <20100329154109.GF5069@bicker> (raw)
In-Reply-To: <20100226.015420.66646406.davem@davemloft.net>
On Fri, Feb 26, 2010 at 01:54:20AM -0800, David Miller wrote:
> From: Dan Carpenter <error27@gmail.com>
> Date: Fri, 26 Feb 2010 12:49:41 +0300
>
> > get_phy_device() can return an ERR_PTR()
> >
> > Signed-off-by: Dan Carpenter <error27@gmail.com>
> > ---
> > I don't have a cross compile environment set up so I can't even compile
> > test this. :/ But err.h is included so it should be OK.
>
> It should return ERR_PTR() consistently. Checking for both
> NULL and ERR_PTR() is undesirable.
Hi Giulio,
get_phy_device() currently returns NULL because of: 3ee82383f0098a2 "phy:
fix phy address bug". If I change it to return ERR_PTR(-ENODEV) that
will mean we break out of the loop with an error in mdiobus_register()
where before we would just continue on.
drivers/net/phy/mdio_bus.c
119 phydev = mdiobus_scan(bus, i);
120 if (IS_ERR(phydev)) {
121 err = PTR_ERR(phydev);
122 goto error;
123 }
Is that OK?
I'm not really familiar with this hardware at all, I'm just going based
on static analysis. :/
regards,
dan carpenter
prev parent reply other threads:[~2010-03-29 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 9:49 [patch] of: check for IS_ERR() Dan Carpenter
2010-02-26 9:54 ` David Miller
2010-02-26 16:11 ` Grant Likely
2010-03-29 15:41 ` Dan Carpenter [this message]
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=20100329154109.GF5069@bicker \
--to=error27@gmail.com \
--cc=afleming@freescale.com \
--cc=davem@davemloft.net \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=giulio.benetti@micronovasrl.com \
--cc=grant.likely@secretlab.ca \
--cc=jeremy.kerr@canonical.com \
--cc=jezz@sysmic.org \
--cc=linux-kernel@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