From: David Miller <davem@davemloft.net>
To: Mark-MC.Lee@mediatek.com
Cc: mark.rutland@arm.com, andrew@lunn.ch,
jakub.kicinski@netronome.com, nelson.chang@mediatek.com,
devicetree@vger.kernel.org, netdev@vger.kernel.org,
sean.wang@mediatek.com, linux-kernel@vger.kernel.org,
opensource@vdorst.com, robh+dt@kernel.org,
linux-mediatek@lists.infradead.org, john@phrozen.org,
matthias.bgg@gmail.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH net,v3 0/2] Update MT7629 to support PHYLINK API
Date: Tue, 15 Oct 2019 18:03:56 -0700 (PDT) [thread overview]
Message-ID: <20191015.180356.268577945716013325.davem@davemloft.net> (raw)
In-Reply-To: <20191014071518.11923-1-Mark-MC.Lee@mediatek.com>
From: MarkLee <Mark-MC.Lee@mediatek.com>
Date: Mon, 14 Oct 2019 15:15:16 +0800
> This patch set has two goals :
> 1. Fix mt7629 GMII mode issue after apply mediatek
> PHYLINK support patch.
> 2. Update mt7629 dts to reflect the latest dt-binding
> with PHYLINK support.
Series applied, thank you.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-10-16 1:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 7:15 [PATCH net,v3 0/2] Update MT7629 to support PHYLINK API MarkLee
2019-10-14 7:15 ` [PATCH net, v3 1/2] net: ethernet: mediatek: Fix MT7629 missing GMII mode support MarkLee
2019-10-15 19:28 ` [PATCH net,v3 " Jakub Kicinski
2019-10-14 7:15 ` [PATCH net, v3 2/2] arm: dts: mediatek: Update mt7629 dts to reflect the latest dt-binding MarkLee
2019-10-16 1:03 ` David Miller [this message]
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=20191015.180356.268577945716013325.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Mark-MC.Lee@mediatek.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=jakub.kicinski@netronome.com \
--cc=john@phrozen.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=nelson.chang@mediatek.com \
--cc=netdev@vger.kernel.org \
--cc=opensource@vdorst.com \
--cc=robh+dt@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).