From: patchwork-bot+netdevbpf@kernel.org
To: Ben Hutchings <ben.hutchings@mind.be>
Cc: steveb@workware.net.au, kuba@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: phy: micrel: Fix link detection on ksz87xx switch"
Date: Sun, 08 Aug 2021 11:10:05 +0000 [thread overview]
Message-ID: <162842100567.27537.2856135053086059450.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210807000618.GB4898@cephalopod>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Sat, 7 Aug 2021 02:06:18 +0200 you wrote:
> Commit a5e63c7d38d5 "net: phy: micrel: Fix detection of ksz87xx
> switch" broke link detection on the external ports of the KSZ8795.
>
> The previously unused phy_driver structure for these devices specifies
> config_aneg and read_status functions that appear to be designed for a
> fixed link and do not work with the embedded PHYs in the KSZ8795.
>
> [...]
Here is the summary with links:
- [net] net: phy: micrel: Fix link detection on ksz87xx switch"
https://git.kernel.org/netdev/net/c/2383cb9497d1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-08-08 11:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 10:51 [PATCH] net: phy: micrel: Fix detection of ksz87xx switch Steve Bennett
2021-07-30 16:59 ` Jakub Kicinski
2021-07-30 22:19 ` Steve Bennett
2021-08-07 0:01 ` Ben Hutchings
2021-08-07 0:06 ` [PATCH net] net: phy: micrel: Fix link detection on ksz87xx switch" Ben Hutchings
2021-08-08 11:10 ` patchwork-bot+netdevbpf [this message]
2021-08-08 22:18 ` [PATCH] net: phy: micrel: Fix detection of ksz87xx switch Steve Bennett
2021-07-30 22:57 ` [PATCH v2] " Steve Bennett
2021-07-30 23:08 ` Marek Vasut
2021-08-02 14:10 ` patchwork-bot+netdevbpf
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=162842100567.27537.2856135053086059450.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ben.hutchings@mind.be \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steveb@workware.net.au \
/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).