devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: chunkeey@googlemail.com
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
	ivan@de.ibm.com, f.fainelli@gmail.com, andrew@lunn.ch,
	robh+dt@kernel.org
Subject: Re: [PATCH v2] dt: emac: document device-tree based phy discovery and setup
Date: Tue, 07 Mar 2017 12:15:28 -0800 (PST)	[thread overview]
Message-ID: <20170307.121528.441751689674246830.davem@davemloft.net> (raw)
In-Reply-To: <0149985a262cfc2feacd604a581cd5ae9134a525.1488228734.git.chunkeey@googlemail.com>

From: Christian Lamparter <chunkeey@googlemail.com>
Date: Mon, 27 Feb 2017 21:54:50 +0100

> This patch adds documentation for a new "phy-handle" property,
> "fixed-link" and "mdio" sub-node. These allows the enumeration
> of PHYs which are supported by the phy library under drivers/net/phy.
> 
> The EMAC ethernet controller in IBM and AMCC 4xx chips is
> currently stuck with a few privately defined phy
> implementations. It has no support for PHYs which
> are supported by the generic phylib.
> 
> Acked-by: Rob Herring <robh@kernel.org>
> Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
> Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>

Applied, thanks.

      reply	other threads:[~2017-03-07 20:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-19 21:22 [PATCH v1 1/2] dt: emac: document device-tree based phy discovery and setup Christian Lamparter
     [not found] ` <8f94c394faf5665ae693f41832f2446dfc7c989e.1487539319.git.chunkeey-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2017-02-19 21:22   ` [PATCH v1 2/2] net: emac: add support for device-tree based PHY " Christian Lamparter
2017-02-20  5:13     ` Florian Fainelli
     [not found]       ` <2109609d-c6a7-5c6f-d6aa-657107765778-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-02-20 19:10         ` [PATCH v1.1] " Christian Lamparter
     [not found]           ` <d32546b59c67456c77d003af1df51862d2f8c5de.1487617501.git.chunkeey-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2017-02-22 20:37             ` David Miller
2017-02-27 19:42               ` Christian Lamparter
2017-02-27 19:54                 ` David Miller
     [not found]                   ` <20170227.145447.1005420963599745103.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2017-02-27 20:11                     ` [PATCH v1.1] dt: emac: document device-tree based phy " Christian Lamparter
     [not found]                       ` <8f94c394faf5665ae693f41832f2446dfc7c989e.1488226061.git.chunkeey-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2017-02-27 20:25                         ` Florian Fainelli
2017-02-27 20:41                           ` [PATCH v1.2] " Christian Lamparter
2017-02-27 20:44                             ` Florian Fainelli
2017-02-27 20:54                               ` [PATCH v2] " Christian Lamparter
2017-03-07 20:15                                 ` David Miller [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=20170307.121528.441751689674246830.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=andrew@lunn.ch \
    --cc=chunkeey@googlemail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=ivan@de.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=robh+dt@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).