From: patchwork-bot+netdevbpf@kernel.org
To: Min Li <min.li.xe@renesas.com>
Cc: richardcochran@gmail.com, lee.jones@linaro.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net v6 1/2] ptp: ptp_clockmatrix: Add PTP_CLK_REQ_EXTTS support
Date: Wed, 18 May 2022 01:00:12 +0000 [thread overview]
Message-ID: <165283561259.28988.13999615912204869168.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1652712427-14703-1-git-send-email-min.li.xe@renesas.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 16 May 2022 10:47:06 -0400 you wrote:
> Use TOD_READ_SECONDARY for extts to keep TOD_READ_PRIMARY
> for gettime and settime exclusively. Before this change,
> TOD_READ_PRIMARY was used for both extts and gettime/settime,
> which would result in changing TOD read/write triggers between
> operations. Using TOD_READ_SECONDARY would make extts
> independent of gettime/settime operation
>
> [...]
Here is the summary with links:
- [net,v6,1/2] ptp: ptp_clockmatrix: Add PTP_CLK_REQ_EXTTS support
https://git.kernel.org/netdev/net-next/c/bec67592521e
- [net,v6,2/2] ptp: ptp_clockmatrix: return -EBUSY if phase pull-in is in progress
https://git.kernel.org/netdev/net-next/c/7c7dcd66c5e0
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:[~2022-05-18 1:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 14:47 [PATCH net v6 1/2] ptp: ptp_clockmatrix: Add PTP_CLK_REQ_EXTTS support Min Li
2022-05-16 14:47 ` [PATCH net v6 2/2] ptp: ptp_clockmatrix: return -EBUSY if phase pull-in is in progress Min Li
2022-05-18 1: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=165283561259.28988.13999615912204869168.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--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