[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250803234200.55698-1-julien@synclab.org>
Date: Sun, 3 Aug 2025 16:42:00 -0700
From: julien@...clab.org
To: richardcochran@...il.com
Cc: akiyano@...zon.com,
aliguori@...zon.com,
alisaidi@...zon.com,
amitbern@...zon.com,
andrew@...n.ch,
benh@...zon.com,
darinzon@...zon.com,
davem@...emloft.net,
dwmw2@...radead.org,
dwmw@...zon.com,
edumazet@...gle.com,
evgenys@...zon.com,
evostrov@...zon.com,
joshlev@...zon.com,
kuba@...nel.org,
matua@...zon.com,
mlichvar@...hat.com,
msw@...zon.com,
nafea@...zon.com,
ndagan@...zon.com,
netanel@...zon.com,
netdev@...r.kernel.org,
ofirt@...zon.com,
pabeni@...hat.com,
ridouxj@...zon.com,
saeedb@...zon.com,
tglx@...utronix.de,
zorik@...zon.com
Subject: RE: [RFC PATCH net-next] ptp: Introduce PTP_SYS_OFFSET_EXTENDED_TRUSTED ioctl
On 7/28/25, 8:55 PM, "Richard Cochran" <richardcochran@...il.com <mailto:richardcochran@...il.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.
Powered by blists - more mailing lists