mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gal Pressman <gal@nvidia.com>
To: patchwork-bot+netdevbpf@kernel.org,
	Kory Maincent <kory.maincent@bootlin.com>
Cc: andrew@lunn.ch, kuba@kernel.org, donald.hunter@gmail.com,
	davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
	horms@kernel.org, willemdebruijn.kernel@gmail.com,
	kernelxing@tencent.com, richardcochran@gmail.com,
	thomas.petazzoni@bootlin.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, maxime.chevallier@bootlin.com,
	linux@armlinux.org.uk
Subject: Re: [PATCH net-next v4] net: Add support for providing the PTP hardware source in tsinfo
Date: Mon, 9 Jun 2025 15:18:49 +0300	[thread overview]
Message-ID: <fd48f64f-dec2-489b-a9b9-dc1aa38ca61d@nvidia.com> (raw)
In-Reply-To: <174792123749.2878676.12488958833707087703.git-patchwork-notify@kernel.org>

On 22/05/2025 16:40, patchwork-bot+netdevbpf@kernel.org wrote:
> Hello:
> 
> This patch was applied to netdev/net-next.git (main)
> by Paolo Abeni <pabeni@redhat.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

  reply	other threads:[~2025-06-09 12:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-19  8:45 Kory Maincent
2025-05-22 13:40 ` patchwork-bot+netdevbpf
2025-06-09 12:18   ` Gal Pressman [this message]
2025-06-09 14:06     ` Kory Maincent

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=fd48f64f-dec2-489b-a9b9-dc1aa38ca61d@nvidia.com \
    --to=gal@nvidia.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kernelxing@tencent.com \
    --cc=kory.maincent@bootlin.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=maxime.chevallier@bootlin.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=patchwork-bot+netdevbpf@kernel.org \
    --cc=richardcochran@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=willemdebruijn.kernel@gmail.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
all inboxes | Powered by JetHome®