From: patchwork-bot+netdevbpf@kernel.org
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, f.fainelli@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, karim.benhoucine@landisgyr.com
Subject: Re: [PATCH] net: phy: micrel: set soft_reset callback to genphy_soft_reset for KSZ8061
Date: Fri, 24 May 2024 11:40:29 +0000 [thread overview]
Message-ID: <171655082948.14489.8867165637123853171.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240521065406.4233-1-othacehe@gnu.org>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Tue, 21 May 2024 08:54:06 +0200 you wrote:
> Following a similar reinstate for the KSZ8081 and KSZ9031.
>
> Older kernels would use the genphy_soft_reset if the PHY did not implement
> a .soft_reset.
>
> The KSZ8061 errata described here:
> https://ww1.microchip.com/downloads/en/DeviceDoc/KSZ8061-Errata-DS80000688B.pdf
> and worked around with 232ba3a51c ("net: phy: Micrel KSZ8061: link failure after cable connect")
> is back again without this soft reset.
>
> [...]
Here is the summary with links:
- net: phy: micrel: set soft_reset callback to genphy_soft_reset for KSZ8061
https://git.kernel.org/netdev/net/c/128d54fbcb14
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-05-24 11:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 6:54 [PATCH] net: phy: micrel: set soft_reset callback to genphy_soft_reset for KSZ8061 Mathieu Othacehe
2024-05-23 9:53 ` Paolo Abeni
2024-05-23 14:15 ` Andrew Lunn
2024-05-23 15:30 ` Florian Fainelli
2024-05-24 11:40 ` 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=171655082948.14489.8867165637123853171.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=karim.benhoucine@landisgyr.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=othacehe@gnu.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).