public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Breno Leitao <leitao@debian.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
	shuah@kernel.org, petrm@nvidia.com, willemb@google.com,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next] selftests: net: py: add test case filtering and listing
Date: Thu, 9 Apr 2026 07:56:17 -0700	[thread overview]
Message-ID: <20260409075617.0b22db0a@kernel.org> (raw)
In-Reply-To: <adedNCKW0WE_FqZK@gmail.com>

On Thu, 9 Apr 2026 05:41:59 -0700 Breno Leitao wrote:
> > +                print(f"Usage: {sys.argv[0]} [-h|-l] [-t|-T name]\n"
> > +                      f"\t-h       print help\n"
> > +                      f"\t-l       list all tests\n"  
> 
> I initially expected the help text to mention "(all or filtered)" based
> on the commit message, but since this option lists all tests
> unconditionally, the current wording is correct.

Ugh, good catch. Not sure how I lost this. It does display a filtered
list. I wanted the filtering to take effect so that one can see what
tests would have been executed with the filters without running them.
Sort of like a --dry-run.

LMK if you have any thoughts on this, otherwise I'll rephrase as:

	 f"\t-l       list tests (filtered, if filters were specified)\n" 
-- 
pw-bot: cr

  reply	other threads:[~2026-04-09 14:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-07 15:17 [PATCH net-next] selftests: net: py: add test case filtering and listing Jakub Kicinski
2026-04-08  0:38 ` Willem de Bruijn
2026-04-09 11:50 ` Gal Pressman
2026-04-09 12:41 ` Breno Leitao
2026-04-09 14:56   ` Jakub Kicinski [this message]
2026-04-09 14:58     ` Breno Leitao

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=20260409075617.0b22db0a@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=leitao@debian.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=petrm@nvidia.com \
    --cc=shuah@kernel.org \
    --cc=willemb@google.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