netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 v6 2/7] net: ethtool: plumb PHY stats to PHY drivers
Date: Thu, 9 Jan 2025 09:48:24 -0800	[thread overview]
Message-ID: <20250109094824.39cef463@kernel.org> (raw)
In-Reply-To: <Z4AHEEX1c0gcGEV6@pengutronix.de>

On Thu, 9 Jan 2025 18:27:44 +0100 Oleksij Rempel wrote:
> > So we traded on set of static inlines for another?
> > What's wrong with adding a C source which is always built in?
> > Like drivers/net/phy/stubs.c, maybe call it drivers/net/phy/accessors.c
> > or drivers/net/phy/helpers.c  
> 
> I chose the current stubs approach based on existing examples like
> hw_timestamps. Any implementation, including the current one, will have
> zero kernel size impact because each function is only used once. While
> moving them to a C source file is an option, it doesn't seem necessary
> given the current usage pattern. Do we really want to spend more time on
> this for something that won’t impact functionality or size? :)

If we keep following existing approaches we'll not have any chance 
to improve :/

But if you feel strongly it's fine. You do need to respin to fix what
Simon pointed out tho, either way.

  reply	other threads:[~2025-01-09 17:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-09  9:44 [PATCH net-next v6 0/7] Introduce unified and structured PHY Oleksij Rempel
2025-01-09  9:44 ` [PATCH net-next v6 1/7] ethtool: linkstate: migrate linkstate functions to support multi-PHY setups Oleksij Rempel
2025-01-09  9:44 ` [PATCH net-next v6 2/7] net: ethtool: plumb PHY stats to PHY drivers Oleksij Rempel
2025-01-09 15:21   ` Simon Horman
2025-01-09 16:07   ` Jakub Kicinski
2025-01-09 17:27     ` Oleksij Rempel
2025-01-09 17:48       ` Jakub Kicinski [this message]
2025-01-10  4:48   ` kernel test robot
2025-01-09  9:44 ` [PATCH net-next v6 3/7] net: ethtool: add support for structured PHY statistics Oleksij Rempel
2025-01-09  9:44 ` [PATCH net-next v6 4/7] Documentation: networking: update PHY error counter diagnostics in twisted pair guide Oleksij Rempel
2025-01-09  9:44 ` [PATCH net-next v6 5/7] net: phy: introduce optional polling interface for PHY statistics Oleksij Rempel
2025-01-09  9:44 ` [PATCH net-next v6 6/7] net: phy: dp83td510: add statistics support Oleksij Rempel
2025-01-09  9:44 ` [PATCH net-next v6 7/7] net: phy: dp83tg720: " Oleksij Rempel

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=20250109094824.39cef463@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 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).