From: julien@synclab.org
To: richardcochran@gmail.com
Cc: akiyano@amazon.com, aliguori@amazon.com, alisaidi@amazon.com,
amitbern@amazon.com, andrew@lunn.ch, benh@amazon.com,
darinzon@amazon.com, davem@davemloft.net, dwmw2@infradead.org,
dwmw@amazon.com, edumazet@google.com, evgenys@amazon.com,
evostrov@amazon.com, joshlev@amazon.com, kuba@kernel.org,
matua@amazon.com, mlichvar@redhat.com, msw@amazon.com,
nafea@amazon.com, ndagan@amazon.com, netanel@amazon.com,
netdev@vger.kernel.org, ofirt@amazon.com, pabeni@redhat.com,
ridouxj@amazon.com, saeedb@amazon.com, tglx@linutronix.de,
zorik@amazon.com
Subject: RE: [RFC PATCH net-next] ptp: Introduce PTP_SYS_OFFSET_EXTENDED_TRUSTED ioctl
Date: Sun, 3 Aug 2025 16:42:00 -0700 [thread overview]
Message-ID: <20250803234200.55698-1-julien@synclab.org> (raw)
In-Reply-To: <aIhGJ9BzR1wY7ij_@hoboy.vegasvil.org>
On 7/28/25, 8:55 PM, "Richard Cochran" <richardcochran@gmail.com <mailto:richardcochran@gmail.com>> wrote:
> On Fri, Jul 25, 2025 at 11:25:24AM +0200, David Woodhouse wrote:
> > The vmclock enlightenment also exposes the same information.
> >
> > David, your RFC should probably have included that implementation
> > shouldn't it?
>
> Yes, a patch series with the new ioctl and two drivers that implement
> it would be more compelling.
We can include the driver side of this RFC for the ENA and vmclock.
next prev parent reply other threads:[~2025-08-03 23:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 11:56 [RFC PATCH net-next] ptp: Introduce PTP_SYS_OFFSET_EXTENDED_TRUSTED ioctl David Arinzon
2025-07-24 14:08 ` David Woodhouse
2025-07-25 4:09 ` Richard Cochran
2025-07-25 9:25 ` David Woodhouse
2025-07-29 3:55 ` Richard Cochran
2025-08-03 23:42 ` julien [this message]
2025-08-08 12:10 ` Maciek Machnikowski
2025-07-28 14:26 ` Miroslav Lichvar
2025-08-03 23:51 ` Julien Ridoux
2025-08-04 9:07 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2025-07-29 2:29 Ridoux, Julien
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=20250803234200.55698-1-julien@synclab.org \
--to=julien@synclab.org \
--cc=akiyano@amazon.com \
--cc=aliguori@amazon.com \
--cc=alisaidi@amazon.com \
--cc=amitbern@amazon.com \
--cc=andrew@lunn.ch \
--cc=benh@amazon.com \
--cc=darinzon@amazon.com \
--cc=davem@davemloft.net \
--cc=dwmw2@infradead.org \
--cc=dwmw@amazon.com \
--cc=edumazet@google.com \
--cc=evgenys@amazon.com \
--cc=evostrov@amazon.com \
--cc=joshlev@amazon.com \
--cc=kuba@kernel.org \
--cc=matua@amazon.com \
--cc=mlichvar@redhat.com \
--cc=msw@amazon.com \
--cc=nafea@amazon.com \
--cc=ndagan@amazon.com \
--cc=netanel@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=ofirt@amazon.com \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=ridouxj@amazon.com \
--cc=saeedb@amazon.com \
--cc=tglx@linutronix.de \
--cc=zorik@amazon.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;
as well as URLs for NNTP newsgroup(s).