From: Wen Gu <guwen@linux.alibaba.com>
To: tglx@kernel.org, tglx@linutronix.de, richardcochran@gmail.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, mani@kernel.org,
imran.shaik@oss.qualcomm.com, John Stultz <jstultz@google.com>,
Anna-Maria Behnsen <anna-maria@linutronix.de>,
Frederic Weisbecker <frederic@kernel.org>,
Daniel Lezcano <daniel.lezcano@kernel.org>,
Stephen Boyd <sboyd@kernel.org>
Cc: 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, dwmw2@infradead.org,
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, taniya.das@oss.qualcomm.com
Subject: Re: [RFC v2 0/2] ptp: Move non-NIC PHC drivers from netdev to clock/timekeeping maintainership
Date: Mon, 9 Mar 2026 14:54:32 +0800 [thread overview]
Message-ID: <c0c9e8a9-1f55-4627-a903-629c9a98cbea@linux.alibaba.com> (raw)
In-Reply-To: <20260227081934.96865-1-guwen@linux.alibaba.com>
On 2026/2/27 16:19, Wen Gu wrote:
To get more clock/timekeeping-side input on this RFC (in particular, the two open
questions below), I’m CC’ing a few additional maintainers from the clock/time area.
> # Request for comments
>
> 1. Following the clocksource/timekeeping and POSIX timer areas, this RFC routes
> changes for drivers/ptp/emulated/ to linux-kernel@vger.kernel.org (rather than
> netdev). However, the preferred integration path is still unclear (e.g. which
> tree should take such changes, and who should collect/pull them for merging). We
> would really appreciate guidance from the time/clock maintainers, especially any
> input from Thomas Gleixner, on the preferred tree/workflow for these changes.
As a concrete option for (1): would it be acceptable to merge changes for
drivers/ptp/emulated/ via tip.git (timers/core branch)?
> 2. This RFC currently lists us as the maintainers for drivers/ptp/emulated/ as a
> fallback contact point. Ideally, we would prefer this area to be maintained by
> clock/time experts in the long run. Suggestions on more suitable maintainers are
> very welcome.
We’d appreciate guidance from the clock/timekeeping maintainers on the preferred
workflow and long-term maintainership for this class of clock drivers.
Thanks!
prev parent reply other threads:[~2026-03-09 6:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 8:19 [RFC v2 0/2] ptp: Move non-NIC PHC drivers from netdev to clock/timekeeping maintainership Wen Gu
2026-02-27 8:19 ` [RFC v2 1/2] ptp: split clock drivers into two subdirectories Wen Gu
2026-02-27 8:19 ` [RFC v2 2/2] MAINTAINERS: update PTP maintainer entries after directory split Wen Gu
2026-02-27 10:25 ` [RFC v2 0/2] ptp: Move non-NIC PHC drivers from netdev to clock/timekeeping maintainership David Woodhouse
2026-02-27 12:25 ` Wen Gu
2026-03-06 2:41 ` Jakub Kicinski
2026-03-09 2:28 ` Wen Gu
2026-03-17 2:12 ` Wen Gu
2026-03-09 6:54 ` Wen Gu [this message]
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=c0c9e8a9-1f55-4627-a903-629c9a98cbea@linux.alibaba.com \
--to=guwen@linux.alibaba.com \
--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=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=tglx@linutronix.de \
--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