From: David Miller <davem@davemloft.net>
To: sean.wang@mediatek.com
Cc: andrew@lunn.ch, Landen.Chao@mediatek.com, f.fainelli@gmail.com,
steven.liu@mediatek.com, vivien.didelot@savoirfairelinux.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
opensource@vdorst.com, linux-mediatek@lists.infradead.org,
john@phrozen.org, Mark-MC.Lee@mediatek.com
Subject: Re: [PATCH v2 net 1/2] net: dsa: mt7530: move mt7623 settings out off the mt7530
Date: Tue, 07 Apr 2020 18:29:31 -0700 (PDT) [thread overview]
Message-ID: <20200407.182931.890813308824136193.davem@davemloft.net> (raw)
In-Reply-To: <1586122974-22125-1-git-send-email-sean.wang@mediatek.com>
From: <sean.wang@mediatek.com>
Date: Mon, 6 Apr 2020 05:42:53 +0800
> From: René van Dorst <opensource@vdorst.com>
>
> Moving mt7623 logic out off mt7530, is required to make hardware setting
> consistent after we introduce phylink to mtk driver.
>
> Fixes: ca366d6c889b ("net: dsa: mt7530: Convert to PHYLINK API")
> Reviewed-by: Sean Wang <sean.wang@mediatek.com>
> Tested-by: Sean Wang <sean.wang@mediatek.com>
> Signed-off-by: René van Dorst <opensource@vdorst.com>
Applied.
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
prev parent reply other threads:[~2020-04-08 1:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 21:42 [PATCH v2 net 1/2] net: dsa: mt7530: move mt7623 settings out off the mt7530 sean.wang
2020-04-05 21:42 ` [PATCH v2 net 2/2] net: ethernet: mediatek: " sean.wang
2020-04-08 1:29 ` David Miller
2020-04-06 13:25 ` Aw: [PATCH v2 net 1/2] net: dsa: mt7530: " Frank Wunderlich
2020-07-23 19:07 ` [PATCH] net: ethernet: mtk_eth_soc: Always call mtk_gmac0_rgmii_adjust() for mt7623 David Woodhouse
2020-07-29 0:05 ` David Miller
2020-07-29 7:30 ` Aw: " Frank Wunderlich
2020-04-08 1:29 ` 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=20200407.182931.890813308824136193.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Landen.Chao@mediatek.com \
--cc=Mark-MC.Lee@mediatek.com \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=john@phrozen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=opensource@vdorst.com \
--cc=sean.wang@mediatek.com \
--cc=steven.liu@mediatek.com \
--cc=vivien.didelot@savoirfairelinux.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).