From: patchwork-bot+netdevbpf@kernel.org
To: Vincent Cheng <vincent.cheng.xh@renesas.com>
Cc: richardcochran@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 net-next 0/7] ptp: ptp_clockmatrix: Fix output 1 PPS alignment.
Date: Wed, 17 Feb 2021 22:00:08 +0000 [thread overview]
Message-ID: <161359920884.16194.18416847721041834914.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1613540538-23792-1-git-send-email-vincent.cheng.xh@renesas.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Wed, 17 Feb 2021 00:42:11 -0500 you wrote:
> From: Vincent Cheng <vincent.cheng.xh@renesas.com>
>
> This series fixes a race condition that may result in the output clock
> not aligned to internal 1 PPS clock.
>
> Part of device initialization is to align the rising edge of output
> clocks to the internal rising edge of the 1 PPS clock. If the system
> APLL and DPLL are not locked when this alignment occurs, the alignment
> fails and a fixed offset between the internal 1 PPS clock and the
> output clock occurs.
>
> [...]
Here is the summary with links:
- [v3,net-next,1/7] ptp: ptp_clockmatrix: Add wait_for_sys_apll_dpll_lock.
https://git.kernel.org/netdev/net-next/c/797d3186544f
- [v3,net-next,2/7] ptp: ptp_clockmatrix: Add alignment of 1 PPS to idtcm_perout_enable.
https://git.kernel.org/netdev/net-next/c/e8b4d8b542b1
- [v3,net-next,3/7] ptp: ptp_clockmatrix: Remove unused header declarations.
https://git.kernel.org/netdev/net-next/c/10c270cf25bd
- [v3,net-next,4/7] ptp: ptp_clockmatrix: Clean-up dev_*() messages.
https://git.kernel.org/netdev/net-next/c/1c49d3e94778
- [v3,net-next,5/7] ptp: ptp_clockmatrix: Coding style - tighten vertical spacing.
https://git.kernel.org/netdev/net-next/c/fcfd37573a09
- [v3,net-next,6/7] ptp: ptp_clockmatrix: Simplify code - remove unnecessary `err` variable.
https://git.kernel.org/netdev/net-next/c/fde3b3a7069e
- [v3,net-next,7/7] ptp: ptp_clockmatrix: clean-up - parenthesis around a == b are unnecessary
https://git.kernel.org/netdev/net-next/c/77fdb168a3e2
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-02-17 22:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 5:42 vincent.cheng.xh
2021-02-17 5:42 ` [PATCH v3 net-next 1/7] ptp: ptp_clockmatrix: Add wait_for_sys_apll_dpll_lock vincent.cheng.xh
2021-02-17 5:42 ` [PATCH v3 net-next 2/7] ptp: ptp_clockmatrix: Add alignment of 1 PPS to idtcm_perout_enable vincent.cheng.xh
2021-02-17 5:42 ` [PATCH v3 net-next 3/7] ptp: ptp_clockmatrix: Remove unused header declarations vincent.cheng.xh
2021-02-17 5:42 ` [PATCH v3 net-next 4/7] ptp: ptp_clockmatrix: Clean-up dev_*() messages vincent.cheng.xh
2021-02-17 5:42 ` [PATCH v3 net-next 5/7] ptp: ptp_clockmatrix: Coding style - tighten vertical spacing vincent.cheng.xh
2021-02-17 5:42 ` [PATCH v3 net-next 6/7] ptp: ptp_clockmatrix: Simplify code - remove unnecessary `err` variable vincent.cheng.xh
2021-02-17 5:42 ` [PATCH v3 net-next 7/7] ptp: ptp_clockmatrix: clean-up - parenthesis around a == b are unnecessary vincent.cheng.xh
2021-02-17 22: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=161359920884.16194.18416847721041834914.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=vincent.cheng.xh@renesas.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®