From: David Miller <davem@davemloft.net>
To: opensource@vdorst.com
Cc: sean.wang@mediatek.com, andrew@lunn.ch, vivien.didelot@gmail.com,
f.fainelli@gmail.com, matthias.bgg@gmail.com,
netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux@armlinux.org.uk,
john@phrozen.org, linux-mips@vger.kernel.org,
frank-w@public-files.de
Subject: Re: [PATCH net-next v3 0/3] net: dsa: mt7530: Convert to PHYLINK and add support for port 5
Date: Wed, 04 Sep 2019 15:28:37 -0700 (PDT) [thread overview]
Message-ID: <20190904.152837.1289570584021077118.davem@davemloft.net> (raw)
In-Reply-To: <20190902130226.26845-1-opensource@vdorst.com>
From: René van Dorst <opensource@vdorst.com>
Date: Mon, 2 Sep 2019 15:02:23 +0200
> 1. net: dsa: mt7530: Convert to PHYLINK API
> This patch converts mt7530 to PHYLINK API.
> 2. dt-bindings: net: dsa: mt7530: Add support for port 5
> 3. net: dsa: mt7530: Add support for port 5
> These 2 patches adding support for port 5 of the switch.
>
> v2->v3:
> * Removed 'status = "okay"' lines in patch #2
> * Change a port 5 setup message in a debug message in patch #3
> * Added ack-by and tested-by tags
> v1->v2:
> * Mostly phylink improvements after review.
> rfc -> v1:
> * Mostly phylink improvements after review.
> * Drop phy isolation patches. Adds no value for now.
Series applied.
prev parent reply other threads:[~2019-09-04 22:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 13:02 [PATCH net-next v3 0/3] net: dsa: mt7530: Convert to PHYLINK and add support for port 5 René van Dorst
2019-09-02 13:02 ` [PATCH net-next v3 1/3] net: dsa: mt7530: Convert to PHYLINK API René van Dorst
2019-09-02 13:02 ` [PATCH net-next v3 2/3] dt-bindings: net: dsa: mt7530: Add support for port 5 René van Dorst
2019-09-03 17:28 ` Rob Herring
2019-09-02 13:02 ` [PATCH net-next v3 3/3] " René van Dorst
2019-09-04 22:28 ` 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=20190904.152837.1289570584021077118.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=frank-w@public-files.de \
--cc=john@phrozen.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=opensource@vdorst.com \
--cc=sean.wang@mediatek.com \
--cc=vivien.didelot@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).