From: Andrew Lunn <andrew@lunn.ch>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Maxime Chevallier <maxime.chevallier@bootlin.com>,
davem@davemloft.net, Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Heiner Kallweit <hkallweit1@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Oleksij Rempel <o.rempel@pengutronix.de>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Florian Fainelli <f.fainelli@gmail.com>,
thomas.petazzoni@bootlin.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH net-next 1/3] selftests: drv-net: Introduce a selftest for ethtool flow control
Date: Thu, 24 Sep 2026 15:54:36 +0200 [thread overview]
Message-ID: <fb18618d-6402-4f7d-b318-1872570ceb27@lunn.ch> (raw)
In-Reply-To: <20260923201051.66e9bf14@kernel.org>
On Wed, Sep 23, 2026 at 08:10:51PM -0700, Jakub Kicinski wrote:
> On Wed, 23 Sep 2026 07:41:13 +0200 Maxime Chevallier wrote:
> > On 9/23/26 04:42, Jakub Kicinski wrote:
> > > On Sun, 20 Sep 2026 18:47:27 +0200 Maxime Chevallier (Netdev
> > > Foundation) wrote:
> > >> Future ethtool selftests are expected to use the same, these helpers
> > >> are put in the net selftest lib.
> > >
> > > Please resist the urge to create libraries.
> > >
> > > If you're doing this I suspect you didn't even read the README and
> > > you expect people to search around for libraries?
> >
> > I did read the README and fought the urge, that was something Andrew
> > was asking for in the previous round :( I'm ok with either TBH.
>
> I guess it was Andrew that didn't read the docs then :)
Yes.
I apply software engineering principles to tests as i would to any
other code. It has to be maintained, bug fixed etc. For my $DAY_JOB, i
spend as much time maintaining test code as feature code. So i don't
really want lots of copy/paste version of the same code.
So, for flow control, lets follow the README. When EEE is implemented,
we can see how bad the copy/paste is, and then consider a library.
Andrew
next prev parent reply other threads:[~2026-09-24 13:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 16:47 [PATCH net-next 0/3] selftests: drv-net: Introduce flow-control selftest Maxime Chevallier (Netdev Foundation)
2026-09-20 16:47 ` [PATCH net-next 1/3] selftests: drv-net: Introduce a selftest for ethtool flow control Maxime Chevallier (Netdev Foundation)
2026-09-23 2:42 ` Jakub Kicinski
2026-09-23 5:41 ` Maxime Chevallier
2026-09-24 3:10 ` Jakub Kicinski
2026-09-24 13:54 ` Andrew Lunn [this message]
2026-09-24 14:02 ` Maxime Chevallier
2026-09-25 13:59 ` Maxime Chevallier
2026-09-25 23:05 ` Jakub Kicinski
2026-09-25 20:31 ` Jakub Kicinski
2026-09-20 16:47 ` [PATCH net-next 2/3] selftests: drv-net: pause: tests against a controllable link partner Maxime Chevallier (Netdev Foundation)
2026-09-20 16:47 ` [PATCH net-next 2/3] selftests: drv-net: pause: Validate the pause autonegotiation with a partner Maxime Chevallier (Netdev Foundation)
2026-09-24 14:03 ` Maxime Chevallier
2026-09-20 16:47 ` [PATCH net-next 3/3] selftests: drv-net: pause: pause autoneg tests Maxime Chevallier (Netdev Foundation)
2026-09-20 16:47 ` [PATCH net-next 3/3] selftests: drv-net: pause: Validate pause autoneg interactions with link autoneg Maxime Chevallier (Netdev Foundation)
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=fb18618d-6402-4f7d-b318-1872570ceb27@lunn.ch \
--to=andrew@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--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 \
--cc=skhan@linuxfoundation.org \
--cc=thomas.petazzoni@bootlin.com \
--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