From: patchwork-bot+netdevbpf@kernel.org
To: Min Li <lnimi@hotmail.com>
Cc: richardcochran@gmail.com, lee@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
min.li.xe@renesas.com
Subject: Re: [PATCH net-next v7 1/2] ptp: introduce PTP_CLOCK_EXTOFF event for the measured external offset
Date: Mon, 29 Jan 2024 13:10:26 +0000 [thread overview]
Message-ID: <170653382637.16154.1775024498484815054.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <PH7PR03MB706498B5804E735C6B681407A07B2@PH7PR03MB7064.namprd03.prod.outlook.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Wed, 24 Jan 2024 13:49:46 -0500 you wrote:
> From: Min Li <min.li.xe@renesas.com>
>
> This change is for the PHC devices that can measure the phase offset
> between PHC signal and the external signal, such as the 1PPS signal of
> GNSS. Reporting PTP_CLOCK_EXTOFF to user space will be piggy-backed to
> the existing ptp_extts_event so that application such as ts2phc can
> poll the external offset the same way as extts. Hence, ts2phc can use
> the offset to achieve the alignment between PHC and the external signal
> by the help of either SW or HW filters.
>
> [...]
Here is the summary with links:
- [net-next,v7,1/2] ptp: introduce PTP_CLOCK_EXTOFF event for the measured external offset
https://git.kernel.org/netdev/net-next/c/ea1cc3ee34a5
- [net-next,v7,2/2] ptp: add FemtoClock3 Wireless as ptp hardware clock
https://git.kernel.org/netdev/net-next/c/1ddfecafabf7
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:[~2024-01-29 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 18:49 Min Li
2024-01-29 13:10 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-05 15:23 Min Li
2024-01-05 17:29 ` Richard Cochran
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=170653382637.16154.1775024498484815054.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lnimi@hotmail.com \
--cc=min.li.xe@renesas.com \
--cc=netdev@vger.kernel.org \
--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 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®