From: Andrew Lunn <andrew@lunn.ch>
To: sean.wang@mediatek.com
Cc: john@phrozen.org, davem@davemloft.net, nbd@openwrt.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH net-next v2 2/4] net-next: mediatek: add platform data to adapt into various hardware
Date: Mon, 17 Jul 2017 15:44:01 +0200 [thread overview]
Message-ID: <20170717134401.GC30392@lunn.ch> (raw)
In-Reply-To: <20170717134309.GB30392@lunn.ch>
On Mon, Jul 17, 2017 at 03:43:09PM +0200, Andrew Lunn wrote:
> > const struct of_device_id of_mtk_match[] = {
> > - { .compatible = "mediatek,mt2701-eth" },
> > + { .compatible = "mediatek,mt2701-eth", .data = &mt2701_data},
> > + { .compatible = "mediatek,mt7623-eth", .data = &mt7623_data},
> > {},
>
> Hi Sean
>
> The binding document also lists "mediatek,mt7622-eth"?
Doh! The next patch adds it. Sorry for the noise.
Andrew
next prev parent reply other threads:[~2017-07-17 13:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 10:06 [PATCH net-next v2 0/4] net-next: mediatek: add support for ethernet on MT7622 SoC sean.wang
2017-07-17 10:06 ` [PATCH net-next v2 1/4] dt-bindings: net: mediatek: add support for MediaTek MT7623 and " sean.wang
2017-07-17 13:38 ` Andrew Lunn
2017-07-18 5:13 ` Sean Wang
[not found] ` <cover.1500285278.git.sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-07-17 10:06 ` [PATCH net-next v2 2/4] net-next: mediatek: add platform data to adapt into various hardware sean.wang-NuS5LvNUpcJWk0Htik3J/w
2017-07-17 13:43 ` Andrew Lunn
2017-07-17 13:44 ` Andrew Lunn [this message]
2017-07-17 10:06 ` [PATCH net-next v2 3/4] net-next: mediatek: add support for MediaTek MT7622 SoC sean.wang-NuS5LvNUpcJWk0Htik3J/w
2017-07-17 10:06 ` [PATCH net-next v2 4/4] MAINTAINERS: add Sean/Nelson as MediaTek ethernet maintainers sean.wang
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=20170717134401.GC30392@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=john@phrozen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=nbd@openwrt.org \
--cc=netdev@vger.kernel.org \
--cc=sean.wang@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).