From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Wagner <wagner.daniel.t@gmail.com>
Cc: netdev@vger.kernel.org, florian.fainelli@broadcom.com,
andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
bcm-kernel-feedback-list@broadcom.com, kuba@kernel.org,
edumazet@google.com, pabeni@redhat.com, nb@tipi-net.de
Subject: Re: [PATCH net-next v3] net: phy: bcm84881: add BCM84891/BCM84892 support
Date: Wed, 01 Apr 2026 02:20:09 +0000 [thread overview]
Message-ID: <177501000978.3035943.17003013654428448756.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260330225310.2801264-1-wagner.daniel.t@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 30 Mar 2026 23:53:10 +0100 you wrote:
> The BCM84891 and BCM84892 are 10GBASE-T PHYs in the same family as the
> BCM84881, sharing the register map and most callbacks. They add USXGMII
> as a host interface mode.
>
> bcm8489x_config_init() is separate from bcm84881_config_init(): it
> allows only USXGMII (the only host mode available on the tested
> hardware) and clears MDIO_CTRL1_LPOWER, which is set at boot on the
> tested platform. Does not recur on ifdown/ifup, cable events, or
> link-partner advertisement changes, so config_init is sufficient.
>
> [...]
Here is the summary with links:
- [net-next,v3] net: phy: bcm84881: add BCM84891/BCM84892 support
https://git.kernel.org/netdev/net-next/c/75171eeff353
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:[~2026-04-01 2:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 22:53 [PATCH net-next v3] net: phy: bcm84881: add BCM84891/BCM84892 support Daniel Wagner
2026-03-30 23:34 ` Russell King (Oracle)
2026-04-01 2:20 ` 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=177501000978.3035943.17003013654428448756.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nb@tipi-net.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wagner.daniel.t@gmail.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