From: Jakub Kicinski <kuba@kernel.org>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Andrew Lunn <andrew@lunn.ch>,
Claudiu Manoil <claudiu.manoil@nxp.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Horatiu Vultur <horatiu.vultur@microchip.com>,
Daniel Machon <daniel.machon@microchip.com>,
UNGLinuxDriver@microchip.com,
Xiaoliang Yang <xiaoliang.yang_1@nxp.com>,
Yangbo Lu <yangbo.lu@nxp.com>,
Richard Cochran <richardcochran@gmail.com>
Subject: Re: [PATCH net-next 0/4] ethtool get_ts_stats() for DSA and ocelot driver
Date: Mon, 16 Dec 2024 18:22:18 -0800 [thread overview]
Message-ID: <20241216182218.5c66e075@kernel.org> (raw)
In-Reply-To: <20241213140852.1254063-1-vladimir.oltean@nxp.com>
On Fri, 13 Dec 2024 16:08:48 +0200 Vladimir Oltean wrote:
> After a recent patch set with fixes and general restructuring, Jakub asked for
> the Felix DSA driver to start reporting standardized statistics for hardware
> timestamping:
> https://lore.kernel.org/netdev/20241207180640.12da60ed@kernel.org/
Looks like we need a rebase.
prev parent reply other threads:[~2024-12-17 2:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 14:08 [PATCH net-next 0/4] ethtool get_ts_stats() for DSA and ocelot driver Vladimir Oltean
2024-12-13 14:08 ` [PATCH net-next 1/4] net: ethtool: ts: add separate counter for unconfirmed one-step TX timestamps Vladimir Oltean
2024-12-13 14:08 ` [PATCH net-next 2/4] net: dsa: implement get_ts_stats ethtool operation for user ports Vladimir Oltean
2024-12-13 14:08 ` [PATCH net-next 3/4] net: mscc: ocelot: add TX timestamping statistics Vladimir Oltean
2024-12-13 14:08 ` [PATCH net-next 4/4] net: dsa: felix: report timestamping stats from the ocelot library Vladimir Oltean
2024-12-14 1:33 ` [PATCH net-next 0/4] ethtool get_ts_stats() for DSA and ocelot driver Jakub Kicinski
2024-12-17 2:22 ` Jakub Kicinski [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=20241216182218.5c66e075@kernel.org \
--to=kuba@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horatiu.vultur@microchip.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=vladimir.oltean@nxp.com \
--cc=xiaoliang.yang_1@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 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.