From: patchwork-bot+netdevbpf@kernel.org
To: Vadim Fedorenko <vadim.fedorenko@linux.dev>
Cc: jonathan.lemon@gmail.com, richardcochran@gmail.com,
kuba@kernel.org, andrew+netdev@lunn.ch, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] ptp_ocp: make ptp_ocp driver compatible with PTP_EXTTS_REQUEST2
Date: Sat, 20 Sep 2025 00:20:22 +0000 [thread overview]
Message-ID: <175832762224.3747217.15356389072519324130.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250918131146.651468-1-vadim.fedorenko@linux.dev>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 18 Sep 2025 13:11:46 +0000 you wrote:
> Originally ptp_ocp driver was not strictly checking flags for external
> timestamper and was always activating rising edge timestamping as it's
> the only supported mode. Recent changes to ptp made it incompatible with
> PTP_EXTTS_REQUEST2 ioctl. Adjust ptp_clock_info to provide supported
> mode and be compatible with new infra.
>
> While at here remove explicit check of periodic output flags from the
> driver and provide supported flags for ptp core to check.
>
> [...]
Here is the summary with links:
- [net-next] ptp_ocp: make ptp_ocp driver compatible with PTP_EXTTS_REQUEST2
https://git.kernel.org/netdev/net-next/c/d3ca2ef0c915
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:[~2025-09-20 0:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 13:11 [PATCH net-next] ptp_ocp: make ptp_ocp driver compatible with PTP_EXTTS_REQUEST2 Vadim Fedorenko
2025-09-20 0:20 ` 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=175832762224.3747217.15356389072519324130.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=vadim.fedorenko@linux.dev \
/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.