From: patchwork-bot+netdevbpf@kernel.org
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: andrew@lunn.ch, linux@armlinux.org.uk, kuba@kernel.org,
davem@davemloft.net, netdev@vger.kernel.org,
zhangchangzhong@huawei.com
Subject: Re: [PATCH net] net: phy: fix duplex out of sync problem while changing settings
Date: Fri, 05 Nov 2021 00:00:08 +0000 [thread overview]
Message-ID: <163607040865.859.15423980570457187665.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <7b8b9456-a93f-abbc-1dc5-a2c2542f932c@gmail.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 3 Nov 2021 22:08:28 +0100 you wrote:
> As reported by Zhang there's a small issue if in forced mode the duplex
> mode changes with the link staying up [0]. In this case the MAC isn't
> notified about the change.
>
> The proposed patch relies on the phylib state machine and ignores the
> fact that there are drivers that uses phylib but not the phylib state
> machine. So let's don't change the behavior for such drivers and fix
> it w/o re-adding state PHY_FORCING for the case that phylib state
> machine is used.
>
> [...]
Here is the summary with links:
- [net] net: phy: fix duplex out of sync problem while changing settings
https://git.kernel.org/netdev/net/c/a4db9055fdb9
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-11-05 0:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 21:08 [PATCH net] net: phy: fix duplex out of sync problem while changing settings Heiner Kallweit
2021-11-05 0:00 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-01 9:44 Zhang Changzhong
2021-11-01 21:37 ` Heiner Kallweit
2021-11-03 8:52 ` Zhang Changzhong
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=163607040865.859.15423980570457187665.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=zhangchangzhong@huawei.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 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.