From: Richard Cochran <richardcochran@gmail.com>
To: Wei Fang <wei.fang@nxp.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, vladimir.oltean@nxp.com,
xiaoning.wang@nxp.com, Frank.Li@nxp.com, yangbo.lu@nxp.com,
christophe.leroy@csgroup.eu, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org, imx@lists.linux.dev
Subject: Re: [PATCH net-next 0/3] ptp: add pulse signal loopback support for debugging
Date: Wed, 3 Sep 2025 06:41:30 -0700 [thread overview]
Message-ID: <aLhFiqHoUnsBAVR7@hoboy.vegasvil.org> (raw)
In-Reply-To: <20250903083749.1388583-1-wei.fang@nxp.com>
On Wed, Sep 03, 2025 at 04:37:46PM +0800, Wei Fang wrote:
> Some PTP devices support looping back the periodic pulse signal for
> debugging,
What kinds of debugs can be resolved by this loopback feature?
It seems pointless to me...
Thanks,
Richard
next prev parent reply other threads:[~2025-09-03 13:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 8:37 [PATCH net-next 0/3] ptp: add pulse signal loopback support for debugging Wei Fang
2025-09-03 8:37 ` [PATCH net-next 1/3] ptp: add debugfs interfaces to loop back the periodic output signal Wei Fang
2025-09-04 13:30 ` Vladimir Oltean
2025-09-03 8:37 ` [PATCH net-next 2/3] ptp: netc: add the periodic output signal loopback support Wei Fang
2025-09-04 13:31 ` Vladimir Oltean
2025-09-03 8:37 ` [PATCH net-next 3/3] ptp: qoriq: covert to use generic interfaces to set loopback mode Wei Fang
2025-09-04 13:35 ` Vladimir Oltean
2025-09-03 13:41 ` Richard Cochran [this message]
2025-09-03 15:11 ` [PATCH net-next 0/3] ptp: add pulse signal loopback support for debugging Vladimir Oltean
2025-09-04 1:55 ` Wei Fang
2025-09-04 13:05 ` Richard Cochran
2025-09-04 13:37 ` Jakub Kicinski
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=aLhFiqHoUnsBAVR7@hoboy.vegasvil.org \
--to=richardcochran@gmail.com \
--cc=Frank.Li@nxp.com \
--cc=andrew+netdev@lunn.ch \
--cc=christophe.leroy@csgroup.eu \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=imx@lists.linux.dev \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vladimir.oltean@nxp.com \
--cc=wei.fang@nxp.com \
--cc=xiaoning.wang@nxp.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;
as well as URLs for NNTP newsgroup(s).