netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Jeremy Linton <jeremy.linton@arm.com>,
	Steve Glendinning <steve.glendinning@shawell.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"tony@atomide.com" <tony@atomide.com>
Subject: Re: [RFC PATCH] smsc911x: Ignore error return from device_get_phy_mode()
Date: Wed, 26 Aug 2015 13:07:15 -0700	[thread overview]
Message-ID: <55DE1C73.7070000@roeck-us.net> (raw)
In-Reply-To: <55DE1735.3070106@arm.com>

On 08/26/2015 12:44 PM, Jeremy Linton wrote:
> On 08/26/2015 01:49 PM, Guenter Roeck wrote:
>> Check the return value from device_property_read_u32() to see if there
>> is a suitable firmware interface to read the data, and abort if not.
>> The function should return -ENXIO in that case; however, it returns
>> -ENODATA. Check for both.
>>
>> Fixes: 62ee783bf1f8 ("smsc911x: Fix crash seen if neither ACPI nor OF is configured or used")
>> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
>> ---
>> Needs testing. RFC because I am not sure if the -ENODATA check is acceptable.
>
> I'm not really sure about it myself. I can think of cases where it might cause problems. That said it does work in an ACPI environment with or without the _DSD block. If the DSD/property isn't set, obviously the device doesn't configure (but it doesn't crash either) so that is good and an overall improvement for ACPI.
>
> Also, I personally might have hoisted the reg-io-width ahead of the device_get_phy_mode() and removed the phy checks, but I don't imagine there is much functional difference at this point.
>
> Tested-by: Jeremy Linton <jeremy.linton@arm.com>
>

I'll post a separate two-patch series which introduces -ENXIO as return value.

Guenter

      reply	other threads:[~2015-08-26 20:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-26 18:49 [RFC PATCH] smsc911x: Ignore error return from device_get_phy_mode() Guenter Roeck
2015-08-26 19:44 ` Jeremy Linton
2015-08-26 20:07   ` Guenter Roeck [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=55DE1C73.7070000@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=jeremy.linton@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=steve.glendinning@shawell.net \
    --cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).