From: patchwork-bot+netdevbpf@kernel.org
To: Russell King (Oracle) <linux@armlinux.org.uk>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com
Subject: Re: [PATCH net-next 0/2] net: phylink: cleanup pcs code
Date: Wed, 29 Jun 2022 04:50:13 +0000 [thread overview]
Message-ID: <165647821362.6492.1196261975874560231.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <YrmYEC2N9mVpg9g6@shell.armlinux.org.uk>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 27 Jun 2022 12:44:16 +0100 you wrote:
> Hi,
>
> These two patches were part of the larger series for the mv88e6xxx
> phylink pcs conversion. As this is delayed, I've decided to send these
> two patches now.
>
> drivers/net/phy/phylink.c | 69 ++++++++++++++++++++++++++---------------------
> 1 file changed, 39 insertions(+), 30 deletions(-)
Here is the summary with links:
- [net-next,1/2] net: phylink: remove pcs_ops member
https://git.kernel.org/netdev/net-next/c/4f1dd48f4031
- [net-next,2/2] net: phylink: disable PCS polling over major configuration
https://git.kernel.org/netdev/net-next/c/bfac8c490d60
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-06-29 4:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 11:44 [PATCH net-next 0/2] net: phylink: cleanup pcs code Russell King (Oracle)
2022-06-27 11:44 ` [PATCH net-next 1/2] net: phylink: remove pcs_ops member Russell King (Oracle)
2022-06-27 11:44 ` [PATCH net-next 2/2] net: phylink: disable PCS polling over major configuration Russell King (Oracle)
2022-06-29 20:03 ` Gerhard Engleder
2022-06-30 9:04 ` 'Re: [PATCH net-next 2/2] net: phylink: disable PCS polling over major configuration' Arun Ramadoss
2022-06-30 10:59 ` Russell King (Oracle)
2022-06-29 4:50 ` 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=165647821362.6492.1196261975874560231.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).