From: Dinh Nguyen <dinguyen@altera.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Dinh Nguyen <dinh.linux@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Richard Cochran <richardcochran@gmail.com>,
Felipe Balbi <balbi@ti.com>,
"David S. Miller" <davem@davemloft.net>,
Giuseppe Cavallaro <peppe.cavallaro@st.com>,
Olof Johansson <olof@lixom.net>,
Rob Herring <rob.herring@calxeda.com>
Subject: Re: [RFC] phy: micrel: Convert micrel PHY driver to use OF
Date: Wed, 21 Aug 2013 15:00:48 -0500 [thread overview]
Message-ID: <1377115248.1554.20.camel@linux-builds1> (raw)
In-Reply-To: <CACRpkdZkyeA5ExvHQPExNBq5qB1hDHON32TO63BmtVrRxDxhXw@mail.gmail.com>
On Thu, 2013-08-15 at 21:55 +0200, Linus Walleij wrote:
> On Tue, Aug 13, 2013 at 6:42 PM, <dinguyen@altera.com> wrote:
>
> > From: Dinh Nguyen <dinguyen@altera.com>
> >
> > Convert the Micrel PHY driver to use OF. This initial patch is only
> > the beginning of an idea to convert the PHY driver to device tree.
> >
> > Signed-of-by: Dinh Nguyen <dinguyen@altera.com>
>
> This is full of device tree stuff so please copy it to
> devicetree@vger.kernel.org.
>
> It seems to add quite a few compatible strings so these should
> be added to the bindings doc, or is it already?
No, there is not a bindings doc yet. I was just trying to see if this is
the right approach..
Thanks,
Dinh
>
> Yours,
> Linus Walleij
>
next prev parent reply other threads:[~2013-08-21 20:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 16:42 [RFC] phy: micrel: Convert micrel PHY driver to use OF dinguyen
2013-08-15 19:55 ` Linus Walleij
2013-08-21 20:00 ` Dinh Nguyen [this message]
2013-08-22 5:13 ` Olof Johansson
2013-08-22 6:34 ` Sascha Hauer
2013-08-22 15:30 ` Dinh Nguyen
2013-08-22 15:30 ` Dinh Nguyen
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=1377115248.1554.20.camel@linux-builds1 \
--to=dinguyen@altera.com \
--cc=balbi@ti.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dinh.linux@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=olof@lixom.net \
--cc=peppe.cavallaro@st.com \
--cc=richardcochran@gmail.com \
--cc=rob.herring@calxeda.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 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.