From: patchwork-bot+netdevbpf@kernel.org
To: Russell King (Oracle) <linux@armlinux.org.uk>
Cc: andrew@lunn.ch, hkallweit1@gmail.com,
claudiu.beznea@microchip.com, davem@davemloft.net,
ioana.ciornei@nxp.com, kuba@kernel.org, mw@semihalf.com,
netdev@vger.kernel.org, nicolas.ferre@microchip.com
Subject: Re: [PATCH net-next 0/2] Add phylink helper for 10G modes
Date: Mon, 04 Oct 2021 13:20:08 +0000 [thread overview]
Message-ID: <163335360802.25690.9874248968746719051.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <YVrfTBYg7cHLzNXM@shell.armlinux.org.uk>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Mon, 4 Oct 2021 12:02:36 +0100 you wrote:
> Hi,
>
> During the last cycle, there was discussion about adding a helper
> to set the 10G link modes for phylink, which resulted in these two
> patches introduce such a helper.
>
> drivers/net/ethernet/cadence/macb_main.c | 7 +------
> drivers/net/ethernet/freescale/dpaa2/dpaa2-mac.c | 7 +------
> drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c | 7 +------
> drivers/net/phy/phylink.c | 11 +++++++++++
> include/linux/phylink.h | 1 +
> 5 files changed, 15 insertions(+), 18 deletions(-)
Here is the summary with links:
- [net-next,1/2] net: phylink: add phylink_set_10g_modes() helper
https://git.kernel.org/netdev/net-next/c/a2c27a61b433
- [net-next,2/2] net: ethernet: use phylink_set_10g_modes()
https://git.kernel.org/netdev/net-next/c/14ad41c74f6b
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:[~2021-10-04 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 11:02 [PATCH net-next 0/2] Add phylink helper for 10G modes Russell King (Oracle)
2021-10-04 11:03 ` [PATCH net-next 1/2] net: phylink: add phylink_set_10g_modes() helper Russell King (Oracle)
2021-10-04 11:03 ` [PATCH net-next 2/2] net: ethernet: use phylink_set_10g_modes() Russell King (Oracle)
2021-10-04 13:20 ` 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=163335360802.25690.9874248968746719051.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=claudiu.beznea@microchip.com \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=ioana.ciornei@nxp.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mw@semihalf.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.