[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fd48f64f-dec2-489b-a9b9-dc1aa38ca61d@nvidia.com>
Date: Mon, 9 Jun 2025 15:18:49 +0300
From: Gal Pressman <gal@...dia.com>
To: patchwork-bot+netdevbpf@...nel.org,
Kory Maincent <kory.maincent@...tlin.com>
Cc: andrew@...n.ch, kuba@...nel.org, donald.hunter@...il.com,
davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com,
horms@...nel.org, willemdebruijn.kernel@...il.com, kernelxing@...cent.com,
richardcochran@...il.com, thomas.petazzoni@...tlin.com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
maxime.chevallier@...tlin.com, linux@...linux.org.uk
Subject: Re: [PATCH net-next v4] net: Add support for providing the PTP
hardware source in tsinfo
On 22/05/2025 16:40, patchwork-bot+netdevbpf@...nel.org wrote:
> Hello:
>
> This patch was applied to netdev/net-next.git (main)
> by Paolo Abeni <pabeni@...hat.com>:
>
> On Mon, 19 May 2025 10:45:05 +0200 you wrote:
>> Multi-PTP source support within a network topology has been merged,
>> but the hardware timestamp source is not yet exposed to users.
>> Currently, users only see the PTP index, which does not indicate
>> whether the timestamp comes from a PHY or a MAC.
>>
>> Add support for reporting the hwtstamp source using a
>> hwtstamp-source field, alongside hwtstamp-phyindex, to describe
>> the origin of the hardware timestamp.
>>
>> [...]
>
> Here is the summary with links:
> - [net-next,v4] net: Add support for providing the PTP hardware source in tsinfo
> https://git.kernel.org/netdev/net-next/c/4ff4d86f6cce
>
> You are awesome, thank you!
Netdev maintainers,
Was there a discussion about merging this without a selftest that covers
this uapi extension? Is this considered an exception?
Thanks
Powered by blists - more mailing lists