From: Tony Lindgren <tony@atomide.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Steve Glendinning <steve.glendinning@shawell.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Jeremy Linton <jeremy.linton@arm.com>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH -next] smsc911x: Fix crash seen if neither ACPI nor OF is configured or used
Date: Wed, 26 Aug 2015 14:40:34 -0700 [thread overview]
Message-ID: <20150826214034.GW4215@atomide.com> (raw)
In-Reply-To: <55DE27BD.600@roeck-us.net>
* Guenter Roeck <linux@roeck-us.net> [150826 13:58]:
> Hi Tony,
>
> On 08/26/2015 01:16 PM, Tony Lindgren wrote:
> [ ... ]
>
> >>We may need two separate patches, one to fix up device_property_read_u32()
> >>to return -ENXIO, and one to fix smsc911x_probe_config() to ignore the error
> >>from device_get_phy_mode(), and to bail out if device_property_read_u32()
> >>returns -ENXIO.
> >
> >I guess the device_property_read_u32() change needs to be discussed
> >separately.. So probably best to fix up the regression to smsc911x
> >first.
> >
> Not sure myself. Jeremy has a point - we don't really know for sure how
> safe it is to check for -ENODATA (in addition to -ENXIO). Also, fixing
> device_property_read_u32() turned out to be much easier than I thought.
>
> >>The simpler alternative would be to check the return value from
> >>device_property_read_u32() for both -ENXIO and -ENODATA.
> >>This would make the code independent of the necessary core changes
> >>(which may take a while). I tested this variant, and it works, at least
> >>for the non-DT case.
> >>
> >>Does this make sense ?
> >
> >Yeh I think that would allow fixing up the smsc911x regression while
> >discussing the device_property_read_u32() change. Got a test patch
> >for me to try?
> >
>
> You should have two by now to choose from.
Acked the second version thanks :)
Tony
prev parent reply other threads:[~2015-08-26 21:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 20:45 [PATCH -next] smsc911x: Fix crash seen if neither ACPI nor OF is configured or used Guenter Roeck
2015-08-17 21:06 ` David Miller
2015-08-17 21:19 ` Jeremy Linton
2015-08-17 22:14 ` Guenter Roeck
2015-08-17 22:35 ` Jeremy Linton
2015-08-26 17:04 ` Tony Lindgren
2015-08-26 17:31 ` Jeremy Linton
2015-08-26 17:48 ` Tony Lindgren
2015-08-26 17:36 ` Guenter Roeck
2015-08-26 17:57 ` Tony Lindgren
2015-08-26 18:34 ` Guenter Roeck
2015-08-26 20:16 ` Tony Lindgren
2015-08-26 20:55 ` Guenter Roeck
2015-08-26 21:40 ` Tony Lindgren [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=20150826214034.GW4215@atomide.com \
--to=tony@atomide.com \
--cc=jeremy.linton@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=netdev@vger.kernel.org \
--cc=steve.glendinning@shawell.net \
/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).