From: patchwork-bot+netdevbpf@kernel.org
To: Russell King (Oracle) <linux@armlinux.org.uk>
Cc: michal.simek@xilinx.com, harinik@xilinx.com,
radhey.shyam.pandey@xilinx.com, davem@davemloft.net,
kuba@kernel.org, linux-arm-kernel@lists.infradead.org,
netdev@vger.kernel.org, sean.anderson@seco.com
Subject: Re: [PATCH net-next 0/2] net: axienet: modernise pcs implementation
Date: Wed, 26 Jan 2022 15:50:12 +0000 [thread overview]
Message-ID: <164321221213.12592.9190321368977882213.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <YfAgeKiKvxcQ0w57@shell.armlinux.org.uk>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 25 Jan 2022 16:08:24 +0000 you wrote:
> Hi,
>
> These two patches modernise the Xilinx axienet PCS implementation to
> use the phylink split PCS support.
>
> The first patch adds split PCS support and makes use of the newly
> introduced mac_select_pcs() function, which is the preferred way to
> conditionally attach a PCS.
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: axienet: convert to phylink_pcs
https://git.kernel.org/netdev/net-next/c/7a86be6a5135
- [net-next,2/2] net: axienet: replace mdiobus_write() with mdiodev_write()
https://git.kernel.org/netdev/net-next/c/03854d8a7723
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-26 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 16:08 [PATCH net-next 0/2] net: axienet: modernise pcs implementation Russell King (Oracle)
2022-01-25 16:10 ` [PATCH net-next 1/2] net: axienet: convert to phylink_pcs Russell King (Oracle)
2022-01-25 16:10 ` [PATCH net-next 2/2] net: axienet: replace mdiobus_write() with mdiodev_write() Russell King (Oracle)
2022-01-26 15: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=164321221213.12592.9190321368977882213.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=harinik@xilinx.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=michal.simek@xilinx.com \
--cc=netdev@vger.kernel.org \
--cc=radhey.shyam.pandey@xilinx.com \
--cc=sean.anderson@seco.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).