From: patchwork-bot+netdevbpf@kernel.org
To: Gatien CHEVALLIER <gatien.chevallier@foss.st.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, mcoquelin.stm32@gmail.com,
alexandre.torgue@foss.st.com, richardcochran@gmail.com,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
jstultz@google.com, tglx@linutronix.de, sboyd@kernel.org,
netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH net-next v4 0/3] net: stmmac: allow generation of flexible PPS relative to MAC time
Date: Thu, 04 Sep 2025 00:30:18 +0000 [thread overview]
Message-ID: <175694581848.1248581.9473792758575091904.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250901-relative_flex_pps-v4-0-b874971dfe85@foss.st.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 1 Sep 2025 11:16:26 +0200 you wrote:
> When doing some testing on stm32mp2x platforms(MACv5), I noticed that
> the command previously used with a MACv4 for genering a PPS signal:
> echo "0 0 0 1 1" > /sys/class/ptp/ptp0/period
> did not work.
>
> This is because the arguments passed through this command must contain
> the start time at which the PPS should be generated, relative to the
> MAC system time. For some reason, a time set in the past seems to work
> with a MACv4.
>
> [...]
Here is the summary with links:
- [net-next,v4,1/3] time: export timespec64_add_safe() symbol
https://git.kernel.org/netdev/net-next/c/96c88268b79b
- [net-next,v4,2/3] drivers: net: stmmac: handle start time set in the past for flexible PPS
https://git.kernel.org/netdev/net-next/c/adbe2cfd8a93
- [net-next,v4,3/3] ARM: dts: stm32: add missing PTP reference clocks on stm32mp13x SoCs
(no matching commit)
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:[~2025-09-04 2:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 9:16 [PATCH net-next v4 0/3] net: stmmac: allow generation of flexible PPS relative to MAC time Gatien Chevallier
2025-09-01 9:16 ` [PATCH net-next v4 1/3] time: export timespec64_add_safe() symbol Gatien Chevallier
2025-09-03 9:57 ` Thomas Gleixner
2025-09-01 9:16 ` [PATCH net-next v4 2/3] drivers: net: stmmac: handle start time set in the past for flexible PPS Gatien Chevallier
2025-09-01 9:16 ` [PATCH net-next v4 3/3] ARM: dts: stm32: add missing PTP reference clocks on stm32mp13x SoCs Gatien Chevallier
2025-09-04 0:30 ` patchwork-bot+netdevbpf [this message]
2025-09-04 11:48 ` [PATCH net-next v4 0/3] net: stmmac: allow generation of flexible PPS relative to MAC time Alexandre TORGUE
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=175694581848.1248581.9473792758575091904.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=gatien.chevallier@foss.st.com \
--cc=jstultz@google.com \
--cc=krzk+dt@kernel.org \
--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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.