From: patchwork-bot+netdevbpf@kernel.org
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Subject: Re: [PATCH net-next] net: phy: micrel: Fix PTP_PF_PEROUT for lan8841
Date: Mon, 17 Apr 2023 07:20:22 +0000 [thread overview]
Message-ID: <168171602237.1935.11467980613738142039.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230414082659.1321686-1-horatiu.vultur@microchip.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 14 Apr 2023 10:26:59 +0200 you wrote:
> If the 1PPS output was enabled and then lan8841 was configured to be a
> follower, then target clock which is used to generate the 1PPS was not
> configure correctly. The problem was that for each adjustments of the
> time, also the nanosecond part of the target clock was changed.
> Therefore the initial nanosecond part of the target clock was changed.
> The issue can be observed if both the leader and the follower are
> generating 1PPS and see that their PPS are not aligned even if the time
> is allined.
> The fix consists of not modifying the nanosecond part of the target
> clock when adjusting the time. In this way the 1PPS get also aligned.
>
> [...]
Here is the summary with links:
- [net-next] net: phy: micrel: Fix PTP_PF_PEROUT for lan8841
https://git.kernel.org/netdev/net-next/c/c6d6ef3ee3b6
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:[~2023-04-17 7:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 8:26 Horatiu Vultur
2023-04-17 7:20 ` 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=168171602237.1935.11467980613738142039.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horatiu.vultur@microchip.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.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
all inboxes | Powered by JetHome®