All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Olof Johansson <olof@lixom.net>
Cc: David Miller <davem@davemloft.net>,
	netdev <netdev@vger.kernel.org>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Aaro Koskinen <aaro.koskinen@nokia.com>
Subject: Re: [PATCH net 2/2] DT: phy.txt: Clarify expected compatible values
Date: Wed, 27 Jan 2016 18:36:44 +0100	[thread overview]
Message-ID: <20160127173644.GJ20194@lunn.ch> (raw)
In-Reply-To: <CAOesGMipfjA9nO8Oe5J_672Xz7nKmR4UAPnoYCBzcZKDiQDFZA@mail.gmail.com>

> Only case I can see the need for a make/model string is if there's a
> need to add model-specific properties since you'd need a compatible
> then (or make those properties shared between all phy bindings).

Documentation/devicetree/bindings/net/micrel-ksz90x1.txt

It adds optional properties to the phy node.

> Anyway, we've never had a huge issue with this on other probable
> busses, so we should be fine with the above. With the clarification
> I'm OK with this change.

Great.

Thanks
	Andrew

      reply	other threads:[~2016-01-27 17:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27  0:11 [PATCH net 0/2] Part 2 of v4.5-rc1 phylib regression Andrew Lunn
2016-01-27  0:11 ` [PATCH net 1/2] of: of_mdio: Add a whitelist of PHY compatibilities Andrew Lunn
2016-01-27 11:17   ` Aaro Koskinen
2016-01-27 13:51   ` Sergei Shtylyov
2016-01-27 14:03     ` Andrew Lunn
2016-01-27  0:11 ` [PATCH net 2/2] DT: phy.txt: Clarify expected compatible values Andrew Lunn
2016-01-27  0:33   ` Florian Fainelli
2016-01-27  1:06     ` Andrew Lunn
2016-01-27  1:25       ` Florian Fainelli
2016-01-27  1:57         ` Andrew Lunn
2016-01-27 16:31           ` Florian Fainelli
2016-01-27 16:41   ` Olof Johansson
2016-01-27 17:11     ` Andrew Lunn
2016-01-27 17:32       ` Olof Johansson
2016-01-27 17:36         ` Andrew Lunn [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=20160127173644.GJ20194@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=aaro.koskinen@nokia.com \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=olof@lixom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.