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/3] Add linkmode_fill, use linkmode_*() in phylink/sfp code
Date: Thu, 16 Nov 2023 23:50:25 +0000 [thread overview]
Message-ID: <170017862524.24110.4750382507758220557.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ZVSt2e9Z5swJNf+7@shell.armlinux.org.uk>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Wed, 15 Nov 2023 11:39:05 +0000 you wrote:
> Hi,
>
> This small series adds a linkmode_fill() op, and uses it in phylink.
> The SFP code is also converted to use linkmode_*() ops.
>
> drivers/net/phy/phylink.c | 4 ++--
> drivers/net/phy/sfp-bus.c | 2 +-
> include/linux/linkmode.h | 5 +++++
> 3 files changed, 8 insertions(+), 3 deletions(-)
Here is the summary with links:
- [net-next,1/3] net: linkmode: add linkmode_fill() helper
https://git.kernel.org/netdev/net-next/c/96fa96e198f9
- [net-next,2/3] net: phylink: use linkmode_fill()
https://git.kernel.org/netdev/net-next/c/ba50a8d40258
- [net-next,3/3] net: sfp: use linkmode_*() rather than open coding
https://git.kernel.org/netdev/net-next/c/466b97b1871a
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:[~2023-11-16 23:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 11:39 [PATCH net-next 0/3] Add linkmode_fill, use linkmode_*() in phylink/sfp code Russell King (Oracle)
2023-11-15 11:39 ` [PATCH net-next 1/3] net: linkmode: add linkmode_fill() helper Russell King (Oracle)
2023-11-15 16:23 ` Andrew Lunn
2023-11-15 11:39 ` [PATCH net-next 2/3] net: phylink: use linkmode_fill() Russell King (Oracle)
2023-11-15 16:23 ` Andrew Lunn
2023-11-15 11:39 ` [PATCH net-next 3/3] net: sfp: use linkmode_*() rather than open coding Russell King (Oracle)
2023-11-15 16:23 ` Andrew Lunn
2023-11-16 23: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=170017862524.24110.4750382507758220557.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 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.