From: Jakub Kicinski <kuba@kernel.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, Simon Horman <horms@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH net-next v4 0/8] Introduce unified and structured PHY
Date: Mon, 23 Dec 2024 10:24:33 -0800 [thread overview]
Message-ID: <20241223102433.55784fa1@kernel.org> (raw)
In-Reply-To: <20241221081530.3003900-1-o.rempel@pengutronix.de>
On Sat, 21 Dec 2024 09:15:22 +0100 Oleksij Rempel wrote:
> This patch set introduces a unified and well-structured interface for
> reporting PHY statistics. Instead of relying on arbitrary strings in PHY
> drivers, this interface provides a consistent and structured way to
> expose PHY statistics to userspace via ethtool.
>
> The initial groundwork for this effort was laid by Jakub Kicinski, who
> contributed patches to plumb PHY statistics to drivers and added support
> for structured statistics in ethtool. Building on Jakub's work, I tested
> the implementation with several PHYs, addressed a few issues, and added
> support for statistics in two specific PHY drivers.
## Form letter - winter-break
Networking development is suspended for winter holidays, until Jan 2nd.
We are currently accepting bug fixes only, see the announcements at:
https://lore.kernel.org/20241211164022.6a075d3a@kernel.org
https://lore.kernel.org/20241220182851.7acb6416@kernel.org
RFC patches sent for review only are welcome at any time.
--
pw-bot: defer
pv-bot: closed
prev parent reply other threads:[~2024-12-23 18:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-21 8:15 [PATCH net-next v4 0/8] Introduce unified and structured PHY Oleksij Rempel
2024-12-21 8:15 ` [PATCH net-next v4 1/8] ethtool: linkstate: migrate linkstate functions to support multi-PHY setups Oleksij Rempel
2024-12-21 8:15 ` [PATCH net-next v4 2/8] net: ethtool: plumb PHY stats to PHY drivers Oleksij Rempel
2024-12-21 8:15 ` [PATCH net-next v4 3/8] net: ethtool: add support for structured PHY statistics Oleksij Rempel
2024-12-21 8:15 ` [PATCH net-next v4 4/8] Documentation: networking: update PHY error counter diagnostics in twisted pair guide Oleksij Rempel
2024-12-21 8:15 ` [PATCH net-next v4 5/8] net: phy: introduce optional polling interface for PHY statistics Oleksij Rempel
2024-12-21 8:15 ` [PATCH net-next v4 6/8] ethtool: add helper to prevent invalid statistics exposure to userspace Oleksij Rempel
2024-12-21 8:15 ` [PATCH net-next v4 7/8] net: phy: dp83td510: add statistics support Oleksij Rempel
2024-12-21 8:15 ` [PATCH net-next v4 8/8] net: phy: dp83tg720: " Oleksij Rempel
2024-12-23 18:24 ` 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=20241223102433.55784fa1@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--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.