From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Vadim Fedorenko <vadim.fedorenko@linux.dev>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Andrei Botila <andrei.botila@oss.nxp.com>,
Richard Cochran <richardcochran@gmail.com>,
Andrew Lunn <andrew@lunn.ch>, Simon Horman <horms@kernel.org>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Jacob Keller <jacob.e.keller@intel.com>,
Kory Maincent <kory.maincent@bootlin.com>,
bcm-kernel-feedback-list@broadcom.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v3 2/9] phy: add hwtstamp_get callback to phy drivers
Date: Wed, 19 Nov 2025 13:24:10 +0000 [thread overview]
Message-ID: <aR3E-mPm_ZWXov8C@shell.armlinux.org.uk> (raw)
In-Reply-To: <20251119124725.3935509-3-vadim.fedorenko@linux.dev>
On Wed, Nov 19, 2025 at 12:47:18PM +0000, Vadim Fedorenko wrote:
> PHY devices had lack of hwtstamp_get callback even though most of them
> are tracking configuration info. Introduce new call back to
> mii_timestamper.
>
> Signed-off-by: Vadim Fedorenko <vadim.fedorenko@linux.dev>
Reviewed-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
Thanks!
--
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-11-19 13:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 12:47 [PATCH net-next v3 0/9] add hwtstamp_get callback to phy drivers Vadim Fedorenko
2025-11-19 12:47 ` [PATCH net-next v3 1/9] phy: rename hwtstamp callback to hwtstamp_set Vadim Fedorenko
2025-11-19 13:23 ` Russell King (Oracle)
2025-11-19 13:50 ` Kory Maincent
2025-11-19 12:47 ` [PATCH net-next v3 2/9] phy: add hwtstamp_get callback to phy drivers Vadim Fedorenko
2025-11-19 13:24 ` Russell King (Oracle) [this message]
2025-11-19 14:09 ` Kory Maincent
2025-11-19 12:47 ` [PATCH net-next v3 3/9] net: phy: broadcom: add HW timestamp configuration reporting Vadim Fedorenko
2025-11-19 14:12 ` Kory Maincent
2025-11-19 12:47 ` [PATCH net-next v3 4/9] net: phy: dp83640: " Vadim Fedorenko
2025-11-19 14:13 ` Kory Maincent
2025-11-19 12:47 ` [PATCH net-next v3 5/9] net: phy: micrel: " Vadim Fedorenko
2025-11-19 14:44 ` Kory Maincent
2025-11-19 15:10 ` Vadim Fedorenko
2025-11-19 15:26 ` Kory Maincent
2025-11-19 12:47 ` [PATCH net-next v3 6/9] net: phy: microchip_rds_ptp: " Vadim Fedorenko
2025-11-19 14:46 ` Kory Maincent
2025-11-19 12:47 ` [PATCH net-next v3 7/9] phy: mscc: " Vadim Fedorenko
2025-11-19 14:48 ` Kory Maincent
2025-11-19 12:47 ` [PATCH net-next v3 8/9] net: phy: nxp-c45-tja11xx: " Vadim Fedorenko
2025-11-19 14:50 ` Kory Maincent
2025-11-19 12:47 ` [PATCH net-next v3 9/9] ptp: ptp_ines: " Vadim Fedorenko
2025-11-19 14:59 ` Kory Maincent
2025-11-19 15:14 ` Vadim Fedorenko
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=aR3E-mPm_ZWXov8C@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrei.botila@oss.nxp.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=vadim.fedorenko@linux.dev \
--cc=vladimir.oltean@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).