From: patchwork-bot+netdevbpf@kernel.org
To: Tariq Toukan <tariqt@nvidia.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, netdev@vger.kernel.org, pabeni@redhat.com,
cjubran@nvidia.com, dtatulea@nvidia.com, gal@nvidia.com,
leon@kernel.org, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org, mbloch@nvidia.com,
rrameshbabu@nvidia.com, richardcochran@gmail.com,
saeedm@nvidia.com, shshitrit@nvidia.com
Subject: Re: [PATCH net] net/mlx5e: Keep HW timestamp stats monotonic across reconfiguration
Date: Sat, 05 Sep 2026 20:30:10 +0000 [thread overview]
Message-ID: <178864021064.1345393.1396917263218162840.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260902193731.3668958-1-tariqt@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 2 Sep 2026 22:37:31 +0300 you wrote:
> From: Carolina Jubran <cjubran@nvidia.com>
>
> `mlx5e_stats_ts_get()` currently selects either DMA or port timestamp
> counters based on `tx_ptp_opened`. This flag is intentionally kept set
> once the PTP TX queues have been opened so their statistics remain
> available after queue teardown. As a result, DMA timestamps are no
> longer reported after switching from port timestamping back to DMA
> timestamping.
>
> [...]
Here is the summary with links:
- [net] net/mlx5e: Keep HW timestamp stats monotonic across reconfiguration
https://git.kernel.org/netdev/net/c/df99553f840e
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:[~2026-09-05 20:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 19:37 [PATCH net] net/mlx5e: Keep HW timestamp stats monotonic across reconfiguration Tariq Toukan
2026-09-05 20:30 ` patchwork-bot+netdevbpf [this message]
2026-09-06 19:00 ` netdev-bot+sashiko
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=178864021064.1345393.1396917263218162840.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=cjubran@nvidia.com \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=rrameshbabu@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=shshitrit@nvidia.com \
--cc=tariqt@nvidia.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 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.