From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Marcin Wojtas <marcin.s.wojtas@gmail.com>,
netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net-next v2] net: mvneta: add support for hardware timestamps
Date: Fri, 12 Sep 2025 09:24:20 +0100 [thread overview]
Message-ID: <aMPYtPj1fpstcbgt@shell.armlinux.org.uk> (raw)
In-Reply-To: <20250911185841.0863ffc0@kernel.org>
On Thu, Sep 11, 2025 at 06:58:41PM -0700, Jakub Kicinski wrote:
> On Thu, 11 Sep 2025 18:55:06 -0700 Jakub Kicinski wrote:
> > On Wed, 10 Sep 2025 13:50:46 +0100 Russell King wrote:
> > > Subject: [PATCH net-next v2] net: mvneta: add support for hardware timestamps
> > > Date: Wed, 10 Sep 2025 13:50:46 +0100
> > > Sender: Russell King <rmk@armlinux.org.uk>
> > >
> > > Add support for hardware timestamps in (e.g.) the PHY by calling
> >
> > These are _software_ timestamps.. (in the subject as well)
> >
> > Fixed when applying.
>
> Let me take that back, you may actually mean HW because of the PHY
> handling detour. Maybe call out both software and PHY (hardware)?
I do mean PHY based hardware timestamps, because that is exactly why
I'm making the change (for my Marvell PHY PTP core.) The software
timestamping is a side effect.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2025-09-12 8:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 12:50 [PATCH net-next v2] net: mvneta: add support for hardware timestamps Russell King
2025-09-12 1:55 ` Jakub Kicinski
2025-09-12 1:58 ` Jakub Kicinski
2025-09-12 8:24 ` Russell King (Oracle) [this message]
2025-09-13 0:10 ` patchwork-bot+netdevbpf
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=aMPYtPj1fpstcbgt@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=marcin.s.wojtas@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.