From: Jakub Kicinski <kuba@kernel.org>
To: Sabrina Dubroca <sd@queasysnail.net>
Cc: Wang Liang <wangliang74@huawei.com>,
andrew@lunn.ch, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, shuah@kernel.org, horms@kernel.org,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, yuehaibing@huawei.com,
zhangchangzhong@huawei.com
Subject: Re: [PATCH net] selftests: netdevsim: Fix ethtool-features.sh fail
Date: Tue, 4 Nov 2025 16:51:21 -0800 [thread overview]
Message-ID: <20251104165121.7069ad66@kernel.org> (raw)
In-Reply-To: <aQnd1HQ-b7wFI2WP@krikkit>
On Tue, 4 Nov 2025 12:04:52 +0100 Sabrina Dubroca wrote:
> So I guess you would lean toward not accepting any such patch, not
> requiring new tests to have SKIP checks, but leaving any existing
> checks in?
Yes, IOW leave it at the discretion of the test author.
> (and I suspect removing all the existing ones wouldn't
> actually reduce the flow of "add check for too old $tool" patches, so
> it probably doesn't make sense to do that)
next prev parent reply other threads:[~2025-11-05 0:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 3:22 [PATCH net] selftests: netdevsim: Fix ethtool-features.sh fail Wang Liang
2025-10-30 23:13 ` Sabrina Dubroca
2025-10-31 0:02 ` Jakub Kicinski
2025-11-03 10:13 ` Sabrina Dubroca
2025-11-03 13:36 ` Andrew Lunn
2025-11-03 15:01 ` Sabrina Dubroca
2025-11-03 15:31 ` Andrew Lunn
2025-11-04 0:01 ` Jakub Kicinski
2025-11-04 11:04 ` Sabrina Dubroca
2025-11-05 0:51 ` Jakub Kicinski [this message]
2025-11-03 8:58 ` Wang Liang
2025-11-03 9:59 ` Sabrina Dubroca
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=20251104165121.7069ad66@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
--cc=shuah@kernel.org \
--cc=wangliang74@huawei.com \
--cc=yuehaibing@huawei.com \
--cc=zhangchangzhong@huawei.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).