From: patchwork-bot+netdevbpf@kernel.org
To: Colin Foster <colin.foster@in-advantage.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux@armlinux.org.uk, hkallweit1@gmail.com,
ioana.ciornei@nxp.com, kuba@kernel.org, davem@davemloft.net,
f.fainelli@gmail.com, vivien.didelot@gmail.com, andrew@lunn.ch,
UNGLinuxDriver@microchip.com, alexandre.belloni@bootlin.com,
claudiu.manoil@nxp.com, vladimir.oltean@nxp.com
Subject: Re: [PATCH v2 net-next 0/5] lynx pcs interface cleanup
Date: Sun, 02 Jan 2022 19:00:11 +0000 [thread overview]
Message-ID: <164115001185.21718.4612917729093758759.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211229050310.1153868-1-colin.foster@in-advantage.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 28 Dec 2021 21:03:05 -0800 you wrote:
> The current Felix driver (and Seville) rely directly on the lynx_pcs
> device. There are other possible PCS interfaces that can be used with
> this hardware, so this should be abstracted from felix. The generic
> phylink_pcs is used instead.
>
> While going through the code, there were some opportunities to change
> some misleading variable names. Those are included in this patch set.
>
> [...]
Here is the summary with links:
- [v2,net-next,1/5] net: phy: lynx: refactor Lynx PCS module to use generic phylink_pcs
https://git.kernel.org/netdev/net-next/c/e7026f15564f
- [v2,net-next,2/5] net: dsa: felix: name change for clarity from pcs to mdio_device
https://git.kernel.org/netdev/net-next/c/61f0d0c304a2
- [v2,net-next,3/5] net: dsa: seville: name change for clarity from pcs to mdio_device
https://git.kernel.org/netdev/net-next/c/2c1415e67f93
- [v2,net-next,4/5] net: ethernet: enetc: name change for clarity from pcs to mdio_device
https://git.kernel.org/netdev/net-next/c/82cc453753c5
- [v2,net-next,5/5] net: pcs: lynx: use a common naming scheme for all lynx_pcs variables
https://git.kernel.org/netdev/net-next/c/0699b3e06f22
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-01-02 19:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 5:03 [PATCH v2 net-next 0/5] lynx pcs interface cleanup Colin Foster
2021-12-29 5:03 ` [PATCH v2 net-next 1/5] net: phy: lynx: refactor Lynx PCS module to use generic phylink_pcs Colin Foster
2021-12-29 5:03 ` [PATCH v2 net-next 2/5] net: dsa: felix: name change for clarity from pcs to mdio_device Colin Foster
2021-12-29 5:03 ` [PATCH v2 net-next 3/5] net: dsa: seville: " Colin Foster
2021-12-29 5:03 ` [PATCH v2 net-next 4/5] net: ethernet: enetc: " Colin Foster
2021-12-29 5:03 ` [PATCH v2 net-next 5/5] net: pcs: lynx: use a common naming scheme for all lynx_pcs variables Colin Foster
2022-01-02 19:00 ` patchwork-bot+netdevbpf [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=164115001185.21718.4612917729093758759.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=colin.foster@in-advantage.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=ioana.ciornei@nxp.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@nxp.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).