From: patchwork-bot+netdevbpf@kernel.org
To: Russell King (Oracle) <linux@armlinux.org.uk>
Cc: Jose.Abreu@synopsys.com, andrew@lunn.ch, davem@davemloft.net,
edumazet@google.com, hkallweit1@gmail.com, kuba@kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net-next 0/2] Clean up pcs-xpcs accessors
Date: Thu, 10 Nov 2022 04:00:16 +0000 [thread overview]
Message-ID: <166805281644.8987.3565993328738914616.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <Y2pm13+SDg6N/IVx@shell.armlinux.org.uk>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 8 Nov 2022 14:25:27 +0000 you wrote:
> Hi,
>
> This series cleans up the pcs-xpcs code to use mdiodev accessors for
> read/write just like xpcs_modify_changed() does. In order to do this,
> we need to introduce the mdiodev clause 45 accessors.
>
> drivers/net/pcs/pcs-xpcs.c | 10 ++--------
> include/linux/mdio.h | 13 +++++++++++++
> 2 files changed, 15 insertions(+), 8 deletions(-)
Here is the summary with links:
- [net-next,1/2] net: mdio: add mdiodev_c45_(read|write)
https://git.kernel.org/netdev/net-next/c/f6479ea4e599
- [net-next,2/2] net: pcs: xpcs: use mdiodev accessors
https://git.kernel.org/netdev/net-next/c/85a2b4ac3444
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-11-10 4:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 14:25 [PATCH net-next 0/2] Clean up pcs-xpcs accessors Russell King (Oracle)
2022-11-08 14:25 ` [PATCH net-next 1/2] net: mdio: add mdiodev_c45_(read|write) Russell King (Oracle)
2022-11-08 15:39 ` Andrew Lunn
2022-11-08 14:26 ` [PATCH net-next 2/2] net: pcs: xpcs: use mdiodev accessors Russell King (Oracle)
2022-11-08 15:40 ` Andrew Lunn
2022-11-10 4: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=166805281644.8987.3565993328738914616.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Jose.Abreu@synopsys.com \
--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).