From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Golle <daniel@makrotopia.org>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 1/3] net: phy: realtek: read duplex and gbit master from PHYSR register
Date: Thu, 17 Oct 2024 07:50:26 +0000 [thread overview]
Message-ID: <172915142679.2078251.79738921563508537.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <b9a76341da851a18c985bc4774fa295babec79bb.1728565530.git.daniel@makrotopia.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 10 Oct 2024 14:07:16 +0100 you wrote:
> The PHYSR MMD register is present and defined equally for all RTL82xx
> Ethernet PHYs.
> Read duplex and Gbit master bits from rtlgen_decode_speed() and rename
> it to rtlgen_decode_physr().
>
> Signed-off-by: Daniel Golle <daniel@makrotopia.org>
>
> [...]
Here is the summary with links:
- [net-next,v2,1/3] net: phy: realtek: read duplex and gbit master from PHYSR register
https://git.kernel.org/netdev/net-next/c/081c9c0265c9
- [net-next,v2,2/3] net: phy: realtek: change order of calls in C22 read_status()
https://git.kernel.org/netdev/net-next/c/68d5cd09e891
- [net-next,v2,3/3] net: phy: realtek: clear 1000Base-T link partner advertisement
https://git.kernel.org/netdev/net-next/c/5cb409b3960e
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:[~2024-10-17 7:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 13:07 [PATCH net-next v2 1/3] net: phy: realtek: read duplex and gbit master from PHYSR register Daniel Golle
2024-10-10 13:07 ` [PATCH net-next v2 2/3] net: phy: realtek: change order of calls in C22 read_status() Daniel Golle
2024-10-10 13:07 ` [PATCH net-next v2 3/3] net: phy: realtek: clear 1000Base-T link partner advertisement Daniel Golle
2024-10-17 7: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=172915142679.2078251.79738921563508537.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.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