netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: grant.likely@secretlab.ca
Cc: scottwood@freescale.com, Joakim.Tjernlund@transmode.se,
	afleming@freescale.com, benh@kernel.crashing.org,
	linuxppc-dev@ozlabs.org, netdev@vger.kernel.org
Subject: Re: [PATCH] net: Fix ucc_geth.c handling of phy 'interface' property.
Date: Tue, 28 Apr 2009 02:12:03 -0700 (PDT)	[thread overview]
Message-ID: <20090428.021203.74435054.davem@davemloft.net> (raw)
In-Reply-To: <fa686aa40904271050kb3159cbw52c0c1dba3076f3e@mail.gmail.com>

From: Grant Likely <grant.likely@secretlab.ca>
Date: Mon, 27 Apr 2009 11:50:20 -0600

> On Mon, Apr 27, 2009 at 11:36 AM, Scott Wood <scottwood@freescale.com> wrote:
>> On Mon, Apr 27, 2009 at 09:36:13AM -0600, Grant Likely wrote:
>>> From: Grant Likely <grant.likely@secretlab.ca>
>>>
>>> Previous rework to ucc_geth.c to add of_mdio support (net: Rework
>>> ucc_geth driver to use of_mdio infrastructure) added a block of
>>> code which broke older openfirmware device trees which use an
>>> 'interface' property in the phy node to describe the connection
>>> between the MAC and the PHY.  This patch removes the offending blurb.
>> [snip]
>>>       prop = of_get_property(np, "phy-connection-type", NULL);
>>>       if (!prop) {
>>>               /* handle interface property present in old trees */
>>> -             if (!phy)
>>> -                     return -ENODEV;
>>> -
>>>               prop = of_get_property(phy, "interface", NULL);
>>>               if (prop != NULL) {
>>>                       phy_interface = enet_to_phy_interface[*prop];
>>
>> The above test only makes a difference when there is no phy node -- so I
>> don't see how it was breaking device trees that had a phy node (with or
>> without an "interface" property).  I can see it breaking fixed link
>> device trees, though.
> 
> Sorry, you're right.  I got myself confused when I was writing the
> description.  This patch fixes breakage when using a fixed-link and
> there is no phy-connection-type property.

Patch applied with commit message fixed up.

  reply	other threads:[~2009-04-28  9:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-27 15:36 [PATCH] net: Fix ucc_geth.c handling of phy 'interface' property Grant Likely
2009-04-27 17:36 ` Scott Wood
2009-04-27 17:50   ` Grant Likely
2009-04-28  9:12     ` David Miller [this message]
2009-04-28 13:37       ` Grant Likely

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=20090428.021203.74435054.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=Joakim.Tjernlund@transmode.se \
    --cc=afleming@freescale.com \
    --cc=benh@kernel.crashing.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=netdev@vger.kernel.org \
    --cc=scottwood@freescale.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).