From: Jakub Kicinski <kuba@kernel.org>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
shuah@kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next 1/2] selftests: drv-net: gro: improve feature config
Date: Sat, 29 Nov 2025 17:13:59 -0800 [thread overview]
Message-ID: <20251129171359.7fd4ddb4@kernel.org> (raw)
In-Reply-To: <willemdebruijn.kernel.2a528ef888696@gmail.com>
On Fri, 28 Nov 2025 15:44:06 -0500 Willem de Bruijn wrote:
> > import os
> > from lib.py import ksft_run, ksft_exit, ksft_pr
> > from lib.py import NetDrvEpEnv, KsftXfailEx
> > -from lib.py import cmd, defer, bkg, ip
> > +from lib.py import cmd, defer, bkg, ethtool, ip
>
> Is there a pattern behind this order. Since inserted rather than
> appended. Intended to be alphabetical?
"alphabetical if I remember"? :(
> > from lib.py import ksft_variants
> >
> >
> > @@ -70,6 +70,27 @@ from lib.py import ksft_variants
> > defer(ip, f"link set dev {dev['ifname']} mtu {dev['mtu']}", host=host)
> >
> >
> > +def _set_ethtool_feat(dev, current, feats, host=None):
> > + s2n = {True: "on", False: "off"}
> > +
> > + new = ["-K", dev]
> > + old = ["-K", dev]
> > + no_change = True
> > + for name, state in feats.items():
> > + new += [name, s2n[state]]
> > + old += [name, s2n[not state]]
>
> Should the change set not only include items for which
> current != state?
>
> Now old assumes not state, but that is not necessarily true?
Good catch
prev parent reply other threads:[~2025-11-30 1:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 0:52 [PATCH net-next 1/2] selftests: drv-net: gro: improve feature config Jakub Kicinski
2025-11-28 0:52 ` [PATCH net-next 2/2] selftests: drv-net: gro: run the test against HW GRO and LRO Jakub Kicinski
2025-11-28 20:42 ` Willem de Bruijn
2025-11-30 1:38 ` Jakub Kicinski
2025-11-30 14:56 ` Willem de Bruijn
2025-12-01 19:50 ` Jakub Kicinski
2025-12-01 21:50 ` Willem de Bruijn
2025-11-28 20:44 ` [PATCH net-next 1/2] selftests: drv-net: gro: improve feature config Willem de Bruijn
2025-11-30 1:13 ` 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=20251129171359.7fd4ddb4@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=willemdebruijn.kernel@gmail.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).