From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
Rob Herring <robherring2@gmail.com>
Cc: netdev <netdev@vger.kernel.org>, Rob Herring <robh+dt@kernel.org>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Rob Landley <rob@landley.net>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
Grant Likely <grant.likely@linaro.org>
Subject: Re: [PATCH] DT: net: document Ethernet bindings in one place
Date: Wed, 22 Jan 2014 00:19:33 +0300 [thread overview]
Message-ID: <52DEE465.9000202@cogentembedded.com> (raw)
In-Reply-To: <CAGVrzcb0dfw1orZzUt5-YkShOg-HNbUYvvo2vfmsZUZXy1Aqfg@mail.gmail.com>
Hello.
On 01/21/2014 11:05 PM, Florian Fainelli wrote:
>>>> I'm afraid that's too late, it has spread very far, so that
>>>> of_get_phy_mode() handles that property, not "phy-connection-type".
>>> Uggg, I guess this is a case of a defacto standard then if the kernel
>>> doesn't even support it.
>> Maybe I forgot to CC you on patch sent to Grant only, I sent a patch a
>> while ago for of_get_phy_mode() to look for both "phy-mode" and
>> "phy-connection-type" since the former has been a Linux invention, but
>> the latter is ePAPR specified.
> Here is a link to the actual patch in question, not sure which tree
> Grant applied it to though:
> http://lkml.indiana.edu/hypermail/linux/kernel/1311.2/00048.html
It's not the patch mail, it's Grant's "applied" reply, patch is mangled in
this reply, and I couldn't follow the thread. Here's the actual patch mail:
http://marc.info/?l=devicetree&m=138449662807254
WBR, Sergei
next prev parent reply other threads:[~2014-01-21 21:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-18 1:05 [PATCH] DT: net: document Ethernet bindings in one place Sergei Shtylyov
[not found] ` < CAL_Jsq+oa9P=rh+p-dMZyGP8TcmpX7bTnMU0ynLvFxjxFDYbRg@mail.gmail.com>
[not found] ` < 52DD98F7.4090202@cogentembedded.com>
[not found] ` < CAL_JsqJXbF1-PcPHR2VP+Vi9A1aWizdsG_r3kDvRt3itXDhCGQ@mail.gmail.com>
[not found] ` < CAGVrzcb3X3soJNJCE5+YSpQrr+EdycCRFkptPvBCgFg4CbGJ4Q@mail.gmail.com>
[not found] ` < CAGVrzcb0dfw1orZzUt5-YkShOg-HNbUYvvo2vfmsZUZXy1Aqfg@mail.gmail.com>
2014-01-20 14:06 ` Rob Herring
2014-01-20 21:45 ` Sergei Shtylyov
2014-01-20 21:20 ` Rob Herring
2014-01-20 23:33 ` Sergei Shtylyov
2014-01-21 19:56 ` Florian Fainelli
2014-01-21 20:05 ` Florian Fainelli
2014-01-21 21:19 ` Sergei Shtylyov [this message]
2014-01-29 23:04 ` Sergei Shtylyov
2014-02-04 17:26 ` Grant Likely
2014-02-04 18:40 ` Sergei Shtylyov
2014-02-05 12:08 ` Grant Likely
[not found] ` < 52F25A63.3010608@cogentembedded.com>
2014-02-05 15:36 ` Sergei Shtylyov
2014-02-06 9:43 ` Grant Likely
2014-02-06 14:06 ` Sergei Shtylyov
2014-02-10 22:05 ` Grant Likely
[not found] ` <20140210220541.C7A56C408F7-WNowdnHR2B42iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
2014-02-14 23:05 ` Sergei Shtylyov
2014-01-22 1:30 ` Rob Herring
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=52DEE465.9000202@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-doc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=pawel.moll@arm.com \
--cc=rob@landley.net \
--cc=robh+dt@kernel.org \
--cc=robherring2@gmail.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).