From: Scott Wood <scottwood@freescale.com>
To: <shh.xie@gmail.com>
Cc: devicetree@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Shaohui Xie <Shaohui.Xie@freescale.com>,
Emilian.Medve@freescale.com
Subject: Re: [PATCH][v4] power/fsl: add MDIO dt binding for FMan
Date: Thu, 29 Jan 2015 18:54:09 -0600 [thread overview]
Message-ID: <1422579249.10544.140.camel@freescale.com> (raw)
In-Reply-To: <1422446064-3901-1-git-send-email-shh.xie@gmail.com>
On Wed, 2015-01-28 at 19:54 +0800, shh.xie@gmail.com wrote:
> +- interrupts
> + Usage: required
> + Value type: <prop-encoded-array>
> + Definition: Event interrupt of external MDIO controller.
What if this MDIO controller is not "external"? Should Usage say
"required for external MDIO"?
-Scott
next prev parent reply other threads:[~2015-01-30 0:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 11:54 [PATCH][v4] power/fsl: add MDIO dt binding for FMan shh.xie
2015-01-30 0:54 ` Scott Wood [this message]
2015-01-30 2:38 ` Shaohui Xie
2015-01-30 2:43 ` Scott Wood
2015-01-30 3:04 ` Shaohui Xie
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=1422579249.10544.140.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=Emilian.Medve@freescale.com \
--cc=Shaohui.Xie@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=shh.xie@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).