From: Jakub Kicinski <kuba@kernel.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Richard Cochran <richardcochran@gmail.com>,
Wen Gu <guwen@linux.alibaba.com>,
tglx@kernel.org, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
jstultz@google.com, anna-maria@linutronix.de,
frederic@kernel.org, daniel.lezcano@kernel.org, sboyd@kernel.org,
vladimir.oltean@nxp.com, wei.fang@nxp.com, xiaoning.wang@nxp.com,
jonathan.lemon@gmail.com, vadim.fedorenko@linux.dev,
yangbo.lu@nxp.com, svens@linux.ibm.com, nick.shi@broadcom.com,
ajay.kaher@broadcom.com, alexey.makhalov@broadcom.com,
bcm-kernel-feedback-list@broadcom.com,
linux-fpga@vger.kernel.org, imx@lists.linux.dev,
linux-s390@vger.kernel.org, dust.li@linux.alibaba.com,
xuanzhuo@linux.alibaba.com, mani@kernel.org,
imran.shaik@oss.qualcomm.com, taniya.das@oss.qualcomm.com
Subject: Re: [PATCH v2 2/2] MAINTAINERS: update PTP maintainer entries after directory split
Date: Tue, 2 Jun 2026 19:03:57 -0700 [thread overview]
Message-ID: <20260602190357.62c04d40@kernel.org> (raw)
In-Reply-To: <0b3f00bbfa6bcc3badb4d1bb7845326e2dbaa1d4.camel@infradead.org>
On Tue, 02 Jun 2026 09:04:27 +0100 David Woodhouse wrote:
> > Even though the "PTP" naming was an unfortunate choice way back when,
> > still I'm not a big fan of moving stuff around "just because".
> >
> > But moving forward, I would suggest starting a new area for pure
> > hardware clock devices.
>
> I think that ties relatively well to Jakub's "does it purport to know
> real time better than the host" criterion?
>
> Although... ENA *both* purports to know real time better than the host
> *and* does packet timestamping, and it looks like GVE is attempting to
> do the same?
FWIW the ENA driver as it exists upstream does not currently support
packet timestamping. Or at least the usual terms for which I'm grepping
do not hit anything in this driver. Only skb_tx_timestamp() which is SW
timestamping
Given various Google projects related to use of time / latency for
networking I think you're right that GVE is likely the first driver
that will straddle the boundary. For those drivers which are both NIC
and virt we can stick to net-next, just always wait for your review?
next prev parent reply other threads:[~2026-06-03 2:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 10:48 [PATCH v2 0/2] ptp: split non-NIC PHC drivers into the clock/timekeeping maintenance domain Wen Gu
2026-04-07 10:48 ` [PATCH v2 1/2] ptp: move emulated/virtual clock drivers into a dedicated subdirectory Wen Gu
2026-04-07 10:48 ` [PATCH v2 2/2] MAINTAINERS: update PTP maintainer entries after directory split Wen Gu
2026-04-12 15:47 ` Jakub Kicinski
2026-04-12 16:32 ` David Woodhouse
2026-04-12 16:53 ` Jakub Kicinski
2026-04-13 9:00 ` Wen Gu
2026-04-29 8:28 ` Wen Gu
2026-05-28 17:06 ` David Woodhouse
2026-06-01 0:20 ` Richard Cochran
2026-06-01 7:03 ` David Woodhouse
2026-06-01 15:20 ` Richard Cochran
2026-06-01 16:53 ` David Woodhouse
2026-06-02 1:52 ` Jakub Kicinski
2026-06-02 4:20 ` Richard Cochran
2026-06-02 8:04 ` David Woodhouse
2026-06-02 14:03 ` Wen Gu
2026-06-02 17:15 ` David Woodhouse
2026-06-03 2:03 ` Jakub Kicinski [this message]
2026-06-02 8:51 ` Wen Gu
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=20260602190357.62c04d40@kernel.org \
--to=kuba@kernel.org \
--cc=ajay.kaher@broadcom.com \
--cc=alexey.makhalov@broadcom.com \
--cc=andrew+netdev@lunn.ch \
--cc=anna-maria@linutronix.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=daniel.lezcano@kernel.org \
--cc=davem@davemloft.net \
--cc=dust.li@linux.alibaba.com \
--cc=dwmw2@infradead.org \
--cc=edumazet@google.com \
--cc=frederic@kernel.org \
--cc=guwen@linux.alibaba.com \
--cc=imran.shaik@oss.qualcomm.com \
--cc=imx@lists.linux.dev \
--cc=jonathan.lemon@gmail.com \
--cc=jstultz@google.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mani@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nick.shi@broadcom.com \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=sboyd@kernel.org \
--cc=svens@linux.ibm.com \
--cc=taniya.das@oss.qualcomm.com \
--cc=tglx@kernel.org \
--cc=vadim.fedorenko@linux.dev \
--cc=vladimir.oltean@nxp.com \
--cc=wei.fang@nxp.com \
--cc=xiaoning.wang@nxp.com \
--cc=xuanzhuo@linux.alibaba.com \
--cc=yangbo.lu@nxp.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