From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Marek_Beh=C3=BAn_=3Ckabel=40kernel=2Eorg=3E?=@ci.codeaurora.org
Cc: netdev@vger.kernel.org, rmk+kernel@armlinux.org.uk,
kuba@kernel.org, andrew@lunn.ch, davem@davemloft.net
Subject: Re: [PATCH net v2 0/2] phylink resolve fixes
Date: Thu, 25 Nov 2021 03:00:09 +0000 [thread overview]
Message-ID: <163780920974.10128.232616050211394190.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211123154403.32051-1-kabel@kernel.org>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 23 Nov 2021 16:44:01 +0100 you wrote:
> With information from me and my nagging, Russell has produced two fixes
> for phylink, which add code that triggers another phylink_resolve() from
> phylink_resolve(), if certain conditions are met:
> interface is being changed
> or
> link is down and previous link was up
> These are needed because sometimes the PCS callbacks may provide stale
> values if link / speed / ...
>
> [...]
Here is the summary with links:
- [net,v2,1/2] net: phylink: Force link down and retrigger resolve on interface change
https://git.kernel.org/netdev/net/c/80662f4fd477
- [net,v2,2/2] net: phylink: Force retrigger in case of latched link-fail indicator
https://git.kernel.org/netdev/net/c/dbae3388ea9c
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:[~2021-11-25 3:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 15:44 [PATCH net v2 0/2] phylink resolve fixes Marek Behún
2021-11-23 15:44 ` [PATCH net v2 1/2] net: phylink: Force link down and retrigger resolve on interface change Marek Behún
2021-11-23 15:44 ` [PATCH net v2 2/2] net: phylink: Force retrigger in case of latched link-fail indicator Marek Behún
2021-11-25 3:00 ` 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=163780920974.10128.232616050211394190.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?Marek_Beh=C3=BAn_=3Ckabel=40kernel=2Eorg=3E?=@ci.codeaurora.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
/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).