From: David Woodhouse <dwmw2@infradead.org>
To: Wen Gu <guwen@linux.alibaba.com>, Jakub Kicinski <kuba@kernel.org>
Cc: tglx@kernel.org, richardcochran@gmail.com, 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: Thu, 28 May 2026 18:06:32 +0100 [thread overview]
Message-ID: <1088b07d760491deb461d6d01abca631e8f8d86c.camel@infradead.org> (raw)
In-Reply-To: <ebf19246-91af-4887-b2aa-d9007921f7b2@linux.alibaba.com>
[-- Attachment #1: Type: text/plain, Size: 2750 bytes --]
On Mon, 2026-04-13 at 17:00 +0800, Wen Gu wrote:
>
> On 2026/4/13 00:53, Jakub Kicinski wrote:
> > On Sun, 12 Apr 2026 17:32:22 +0100 David Woodhouse wrote:
> > > On 12 April 2026 16:47:04 BST, Jakub Kicinski <kuba@kernel.org> wrote:
> > > > On Tue, 7 Apr 2026 18:48:02 +0800 Wen Gu wrote:
> > > > > +PTP EMULATED CLOCK SUPPORT
> > > > > +M: David Woodhouse <dwmw2@infradead.org>
> > > > > +M: Wen Gu <guwen@linux.alibaba.com>
> > > > > +M: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
> > > > > +L: linux-kernel@vger.kernel.org
> > > > > +S: Maintained
> > > > > +T: git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers/core
> > > >
> > > > Hi David,
> > > >
> > > > Do you have a tree to route the patches thru? Or do you really have
> > > > access to the tip tree?
> > >
> > > I do not have access to the tip tree. I can make a shared tree on
> > > git.infradead.org if the other two maintainers would like to send me
> > > a SSH pubkey and preferred username...
> >
> > Honestly I'd love for you to be the only M here, and the other two
> > to be reviewers. Xuan Zhuo is currently at v40 trying to upstream
> > an Ethernet driver. Some growth needed there to become a subsystem
> > maintainer IMO.
>
> Hi Jakub, David,
>
> That works for us. We can act as reviewers.
>
> If David sets up a new tree, I will update the MAINTAINERS entry
> accordingly in v3.
Apologies for the delay. I have set up
https://git.infradead.org/?p=linux-ptp.git
git://git.infradead.org/linux-ptp.git
But I'm not keen on using it without Richard's explicit approval and a
clear understanding of who owns what, *and* the taxonomy we use...
I'm not entirely keen on 'emulated' as the directory name. I don't want
to get too bogged down in bikeshedding, and I know we've done some
already, but I think 'virt' is a better fit? Although when I get my
hands on one of those PTM-capable TimeCards, vmclock won't *just* be
virt... :)
I'm not sure I agree that the drivers being left behind in drivers/ptp
are "IEEE1588 / network-oriented clock drivers" as the commit message
of patch 1 suggests, either. The only one that goes anywhere *near* a
network is ptp_ines.c which has a mii_timestamper interface.
Apart from that they are *all* just PHC clock drivers, aren't they? The
actual network ones live in drivers/net.
So maybe the better answer is to have a more conventional core/drivers
split? Except maybe for ptp_ines is there anything that *network*
maintainers care about, other than the core?
If we do that, add an X: line to exclude the drivers subdir from the
network section in MAINTAINERS, and leave all of drivers/ptp owned by
Richard as it is... do we *need* a new tree?
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5069 bytes --]
next prev parent reply other threads:[~2026-05-28 17:06 UTC|newest]
Thread overview: 21+ 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 [this message]
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
2026-06-03 22:55 ` David Woodhouse
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=1088b07d760491deb461d6d01abca631e8f8d86c.camel@infradead.org \
--to=dwmw2@infradead.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=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=kuba@kernel.org \
--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