From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?Q3PDs2vDoXMgQmVuY2UgPGNzb2thcy5iZW5jZUBwcm9sYW4uaHU+?=@ci.codeaurora.org
Cc: netdev@vger.kernel.org, richardcochran@gmail.com,
davem@davemloft.net, kuba@kernel.org, qiangqing.zhang@nxp.com,
andrew@lunn.ch
Subject: Re: [PATCH v3 resubmit] fec: Restart PPS after link state change
Date: Wed, 24 Aug 2022 09:00:15 +0000 [thread overview]
Message-ID: <166133161533.23661.112567039539561723.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220822081051.7873-1-csokas.bence@prolan.hu>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Mon, 22 Aug 2022 10:10:52 +0200 you wrote:
> On link state change, the controller gets reset,
> causing PPS to drop out and the PHC to lose its
> time and calibration. So we restart it if needed,
> restoring calibration and time registers.
>
> Changes since v2:
> * Add `fec_ptp_save_state()`/`fec_ptp_restore_state()`
> * Use `ktime_get_real_ns()`
> * Use `BIT()` macro
> Changes since v1:
> * More ECR #define's
> * Stop PPS in `fec_ptp_stop()`
>
> [...]
Here is the summary with links:
- [v3,resubmit] fec: Restart PPS after link state change
https://git.kernel.org/netdev/net/c/f79959220fa5
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:[~2022-08-24 9:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 8:10 [PATCH v3 resubmit] fec: Restart PPS after link state change Csókás Bence
2022-08-24 9:00 ` patchwork-bot+netdevbpf [this message]
2022-08-27 16:09 ` BUG: " Marc Kleine-Budde
2022-09-05 18:05 ` Guenter Roeck
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=166133161533.23661.112567039539561723.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?Q3PDs2vDoXMgQmVuY2UgPGNzb2thcy5iZW5jZUBwcm9sYW4uaHU+?=@ci.codeaurora.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=qiangqing.zhang@nxp.com \
--cc=richardcochran@gmail.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.