From: Rob Herring <robh@kernel.org>
To: John Crispin <blogic@openwrt.org>
Cc: "David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
"Steven Liu (劉人豪)" <steven.liu@mediatek.com>,
"Carlos Huang (黃士彰)" <Carlos.Huang@mediatek.com>,
"Felix Fietkau" <nbd@openwrt.org>,
"Michael Lee" <igvtee@gmail.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH V3 1/4] net-next: mediatek: document MediaTek SoC ethernet binding
Date: Fri, 4 Mar 2016 22:30:16 -0600 [thread overview]
Message-ID: <20160305043016.GD13525@rob-hp-laptop> (raw)
In-Reply-To: <1457035361-57669-2-git-send-email-blogic@openwrt.org>
On Thu, Mar 03, 2016 at 09:02:38PM +0100, John Crispin wrote:
> This adds the binding documentation for the MediaTek Ethernet
> controller.
>
> Signed-off-by: John Crispin <blogic@openwrt.org>
> Cc: devicetree@vger.kernel.org
> ---
> .../devicetree/bindings/net/mediatek-net.txt | 77 ++++++++++++++++++++
> 1 file changed, 77 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/net/mediatek-net.txt
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2016-03-05 4:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 20:02 [PATCH V3 0/4] net-next: mediatek: add ethernet driver John Crispin
2016-03-03 20:02 ` [PATCH V3 1/4] net-next: mediatek: document MediaTek SoC ethernet binding John Crispin
2016-03-05 4:30 ` Rob Herring [this message]
2016-03-03 20:02 ` [PATCH V3 2/4] net-next: mediatek: add support for MT7623 ethernet John Crispin
2016-03-03 21:06 ` Joe Perches
2016-03-04 10:50 ` David Laight
2016-03-03 20:02 ` [PATCH V3 3/4] net-next: mediatek: add Kconfig and Makefile John Crispin
2016-03-03 20:02 ` [PATCH V3 4/4] net-next: mediatek: add an entry to MAINTAINERS John Crispin
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=20160305043016.GD13525@rob-hp-laptop \
--to=robh@kernel.org \
--cc=Carlos.Huang@mediatek.com \
--cc=blogic@openwrt.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=igvtee@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=nbd@openwrt.org \
--cc=netdev@vger.kernel.org \
--cc=steven.liu@mediatek.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).