From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: sunder ramani <sunder.svit-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org,
devicetree-discuss list
<devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org>,
afleming-KZfg59tc24xl57MIdRCFDg@public.gmane.org
Subject: Re: [PATCH 1/9] of: add of_parse_phandle() helper for parsing
Date: Thu, 19 Mar 2009 00:01:02 -0600 [thread overview]
Message-ID: <fa686aa40903182301l63d9319r40a9e8e20f89af5a@mail.gmail.com> (raw)
In-Reply-To: <d90126080903182237i6057e9afi9051723685bcb2d2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Wed, Mar 18, 2009 at 11:37 PM, sunder ramani <sunder.svit-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> To Summarize, should not we have a phy_type flag in the OF tree which
> will let the PHY layer do the various PHY tasks based on if it is a
> copper/fiber interface. I really dont like my fix in my kernel and am
> new to open source. Do you think it is a valid argument? If it so, I
> would like to plan to introduce those changes and post to the
> community.
Yes, we probably do need some form of flag here for describing the PHY
interface. Feel free to post a suggested binding for this.
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next parent reply other threads:[~2009-03-19 6:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d90126080903182237i6057e9afi9051723685bcb2d2@mail.gmail.com>
[not found] ` <d90126080903182237i6057e9afi9051723685bcb2d2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-03-19 6:01 ` Grant Likely [this message]
2009-03-19 6:05 ` [PATCH 1/9] of: add of_parse_phandle() helper for parsing sunder ramani
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=fa686aa40903182301l63d9319r40a9e8e20f89af5a@mail.gmail.com \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
--cc=afleming-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
--cc=linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
--cc=sunder.svit-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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