From: patchwork-bot+netdevbpf@kernel.org
To: Gan Yi Fang <yi.fang.gan@intel.com>
Cc: peppe.cavallaro@st.com, alexandre.torgue@foss.st.com,
joabreu@synopsys.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, mcoquelin.stm32@gmail.com,
richardcochran@gmail.com, netdev@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, hong.aun.looi@intel.com,
weifeng.voon@intel.com, pei.lee.ling@intel.com,
tee.min.tan@intel.com, muhammad.husaini.zulkifli@intel.com,
michael.wei.hong.sit@intel.com
Subject: Re: [PATCH net 1/1] stmmac: intel: Update PCH PTP clock rate from 200MHz to 204.8MHz
Date: Thu, 10 Nov 2022 02:50:14 +0000 [thread overview]
Message-ID: <166804861412.6959.10905430097116561347.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221108020811.12919-1-yi.fang.gan@intel.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 7 Nov 2022 21:08:11 -0500 you wrote:
> From: "Tan, Tee Min" <tee.min.tan@intel.com>
>
> Current Intel platform has an output of ~976ms interval
> when probed on 1 Pulse-per-Second(PPS) hardware pin.
>
> The correct PTP clock frequency for PCH GbE should be 204.8MHz
> instead of 200MHz. PSE GbE PTP clock rate remains at 200MHz.
>
> [...]
Here is the summary with links:
- [net,1/1] stmmac: intel: Update PCH PTP clock rate from 200MHz to 204.8MHz
https://git.kernel.org/netdev/net/c/dcea1a8107c0
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-11-10 2:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 2:08 [PATCH net 1/1] stmmac: intel: Update PCH PTP clock rate from 200MHz to 204.8MHz Gan Yi Fang
2022-11-10 2:50 ` 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=166804861412.6959.10905430097116561347.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hong.aun.looi@intel.com \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=michael.wei.hong.sit@intel.com \
--cc=muhammad.husaini.zulkifli@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pei.lee.ling@intel.com \
--cc=peppe.cavallaro@st.com \
--cc=richardcochran@gmail.com \
--cc=tee.min.tan@intel.com \
--cc=weifeng.voon@intel.com \
--cc=yi.fang.gan@intel.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