From: patchwork-bot+netdevbpf@kernel.org
To: Florian Larysch <fl@n621.de>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, Divya.Koppera@microchip.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH net] net: phy: micrel: fix KSZ8081/KSZ8091 cable test
Date: Fri, 25 Jul 2025 22:17:23 +0000 [thread overview]
Message-ID: <175348184349.3265195.8359629740044567911.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250723222250.13960-1-fl@n621.de>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 24 Jul 2025 00:20:42 +0200 you wrote:
> Commit 21b688dabecb ("net: phy: micrel: Cable Diag feature for lan8814
> phy") introduced cable_test support for the LAN8814 that reuses parts of
> the KSZ886x logic and introduced the cable_diag_reg and pair_mask
> parameters to account for differences between those chips.
>
> However, it did not update the ksz8081_type struct, so those members are
> now 0, causing no pairs to be tested in ksz886x_cable_test_get_status
> and ksz886x_cable_test_wait_for_completion to poll the wrong register
> for the affected PHYs (Basic Control/Reset, which is 0 in normal
> operation) and exit immediately.
>
> [...]
Here is the summary with links:
- [net] net: phy: micrel: fix KSZ8081/KSZ8091 cable test
https://git.kernel.org/netdev/net/c/49db61c27c4b
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:[~2025-07-25 22:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 22:20 [PATCH net] net: phy: micrel: fix KSZ8081/KSZ8091 cable test Florian Larysch
2025-07-25 22:17 ` 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=175348184349.3265195.8359629740044567911.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Divya.Koppera@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fl@n621.de \
--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 \
--cc=stable@vger.kernel.org \
/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.