From: Nikolai Kondrashov <Nikolai.Kondrashov@redhat.com>
To: workflows@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Joe Perches <joe@perches.com>, Andy Whitcroft <apw@canonical.com>,
Theodore Ts'o <tytso@mit.edu>, David Gow <davidgow@google.com>,
Steven Rostedt <rostedt@goodmis.org>,
Mark Brown <broonie@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
"Darrick J . Wong" <djwong@kernel.org>
Cc: kunit-dev@googlegroups.com, linux-kselftest@vger.kernel.org,
Veronika Kabatova <vkabatov@redhat.com>,
CKI <cki-project@redhat.com>,
kernelci@lists.linux.dev
Subject: [RFC PATCH v2 00/10] MAINTAINERS: Introduce V: entry for tests
Date: Tue, 5 Dec 2023 20:02:56 +0200 [thread overview]
Message-ID: <20231205184503.79769-1-Nikolai.Kondrashov@redhat.com> (raw)
In-Reply-To: <20231115175146.9848-1-Nikolai.Kondrashov@redhat.com>
Alright, here's a second version, attempting to address as many concerns as
possible. It's likely I've missed something, though.
Changes from v1:
* Make scripts/get_maintainer.pl survive querying missing files, giving a
warning instead. This is necessary to enable scripts/checkpatch.pl to query
MAINTAINERS about files being deleted.
* Start with the minimal change just documenting the V: entry, which accepts
test commands directly, and tweaking the tools to deal with that.
* However, require the commands accept the -h/--help option so that users have
an easier time getting *some* help. The run_checks.py missing that is the
reason why the patch proposing it for kunit subsystem is marked "DONOTMERGE"
in this version. We can drop that requirement, or soften the language, if
there's opposition.
* Have a *separate* patch documenting 'Tested-with:' as the next (early)
change. Mention that you can add a '#' followed by a results URL, on the
end. Adjust the V: docs/checks to exclude '#'.
* Have a *separate* patch making scripts/checkpatch.pl propose the execution
of the test suite defined in MAINTAINERS whenever the corresponding
subsystem is changed.
* However, use 'CHECK', instead of 'WARNING', to allow submitters specify the
exact (and potentially slightly different) command they used, and not have
checkpatch.pl complain too loudly that they didn't run the (exact
MAINTAINERS-specified) command. This unfortunately means that unless you use
--strict, you won't see the message. We'll try to address that in a new
change at the end.
* Have a *separate* patch introducing the test catalog and accepting
references to that everywhere, with a special syntax to distinguish them
from verbatim/direct commands. The syntax is prepending the test name with a
'*' (just like C pointer dereference). Make checkpatch.pl handle that.
* Drop the recommendation to have the "Docs" and "Sources" fields in test
descriptions, as the description text should focus on giving a good
introduction and not prompt the user to go somewhere else immediately. They
both can be referenced in the text where and how is appropriate.
* Generally keep the previous changes adding V: entries and test suite docs,
and try to accommodate all the requests, but refine the "Summary" fields to
fit the checkpatch.pl messages better.
* Have a separate patch cataloguing the complete kunit suite.
* Finally, add a patch introducing the "proposal strength" keywords
(SUGGESTED/RECOMMENDED/REQUIRED) to the syntax of V: entries, which directly
affect which level of checkpatch.pl message missing 'Tested-with:' tags
would generate: CHECK/WARNING/ERROR respectively. This allows subsystems to
disable checkpatch.pl WARNINGS/ERRORS, and keep their test proposals
inobtrusive, if they so wish. E.g. if they expect people to change their
commands often. At the same time allow stricter workflows for subsystems
with more uniform testing. Or e.g. for subsystems which expect the tests to
explain their parameters in their output, and the submitters to upload and
link their results in their 'Tested-with:' tags.
That seems to be all, but I'm sure I forgot something :D
Anyway, send me more corrections and I'll try to address them, but it's likely
going to happen next year only.
Nick
---
Nikolai Kondrashov (9):
get_maintainer: Survive querying missing files
MAINTAINERS: Introduce V: entry for tests
MAINTAINERS: Propose kunit core tests for framework changes
docs: submitting-patches: Introduce Tested-with:
checkpatch: Propose tests to execute
MAINTAINERS: Support referencing test docs in V:
MAINTAINERS: Propose kvm-xfstests smoke for ext4
docs: tests: Document kunit in general
MAINTAINERS: Add proposal strength to V: entries
Mark Brown (1):
MAINTAINERS: Propose kunit tests for regmap
Documentation/process/index.rst | 1 +
Documentation/process/submitting-patches.rst | 46 +++++++
Documentation/process/tests.rst | 96 +++++++++++++++
MAINTAINERS | 17 +++
scripts/checkpatch.pl | 174 ++++++++++++++++++++++++++-
scripts/get_maintainer.pl | 23 +++-
scripts/parse-maintainers.pl | 3 +-
7 files changed, 355 insertions(+), 5 deletions(-)
---
next prev parent reply other threads:[~2023-12-05 18:45 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 17:43 [RFC PATCH 0/3] MAINTAINERS: Introduce V: field for required tests Nikolai Kondrashov
2023-11-15 17:43 ` [PATCH 1/3] " Nikolai Kondrashov
2023-11-15 18:31 ` Joe Perches
2023-11-15 20:01 ` Mark Brown
2023-11-16 12:00 ` Nikolai Kondrashov
2023-11-15 20:14 ` Mark Brown
2023-11-16 12:09 ` Nikolai Kondrashov
2023-11-15 20:38 ` Konstantin Ryabitsev
2023-11-16 12:14 ` Nikolai Kondrashov
2023-11-16 13:26 ` Mark Brown
2023-11-16 13:52 ` Nikolai Kondrashov
2023-11-20 12:40 ` Gustavo Padovan
2023-11-20 13:31 ` Mark Brown
2023-11-22 17:41 ` Nikolai Kondrashov
2023-11-16 13:20 ` Bagas Sanjaya
2023-11-16 13:41 ` Nikolai Kondrashov
2023-11-16 13:43 ` Bagas Sanjaya
2023-11-16 13:59 ` Greg Kroah-Hartman
2023-11-16 14:21 ` Geert Uytterhoeven
2023-11-20 13:30 ` Ricardo Cañuelo
2023-11-20 20:51 ` Theodore Ts'o
2023-11-20 22:27 ` Mark Brown
2023-11-21 6:04 ` Theodore Ts'o
2023-11-21 10:37 ` David Gow
2023-11-21 13:27 ` Mark Brown
2023-11-22 16:16 ` Theodore Ts'o
2023-11-21 18:24 ` Nikolai Kondrashov
2023-11-21 18:02 ` Nikolai Kondrashov
2023-11-21 10:36 ` David Gow
2023-11-21 20:48 ` Mark Brown
2023-11-22 17:19 ` Nikolai Kondrashov
2023-11-22 1:08 ` kernel test robot
2023-11-15 17:43 ` [PATCH 2/3] MAINTAINERS: Require kvm-xfstests smoke for ext4 Nikolai Kondrashov
2023-11-15 18:58 ` Darrick J. Wong
2023-11-16 16:33 ` Nikolai Kondrashov
2023-11-17 7:09 ` Chandan Babu R
2023-11-19 22:54 ` Theodore Ts'o
2023-11-22 14:44 ` Nikolai Kondrashov
2023-11-22 16:17 ` Darrick J. Wong
2023-11-22 17:44 ` Nikolai Kondrashov
2023-11-22 20:51 ` Dave Chinner
2023-11-15 17:43 ` [PATCH 3/3] MAINTAINERS: Require kunit core tests for framework changes Nikolai Kondrashov
2023-11-20 18:48 ` Daniel Latypov
2023-11-22 17:38 ` Nikolai Kondrashov
2023-12-05 18:02 ` Nikolai Kondrashov [this message]
2023-12-05 18:02 ` [RFC PATCH v2 01/10] get_maintainer: Survive querying missing files Nikolai Kondrashov
2023-12-05 18:55 ` Joe Perches
2023-12-06 16:16 ` Nikolai Kondrashov
2024-01-31 13:55 ` Nikolai Kondrashov
2023-12-05 18:02 ` [RFC PATCH v2 02/10] MAINTAINERS: Introduce V: entry for tests Nikolai Kondrashov
2023-12-05 18:58 ` Joe Perches
2023-12-06 16:21 ` Nikolai Kondrashov
2023-12-06 8:12 ` David Gow
2023-12-06 16:23 ` Nikolai Kondrashov
2023-12-06 16:38 ` Joe Perches
2023-12-06 16:57 ` Nikolai Kondrashov
2023-12-05 18:02 ` [RFC PATCH v2 03/10] MAINTAINERS: Propose kunit core tests for framework changes Nikolai Kondrashov
2023-12-05 18:03 ` [RFC PATCH v2 04/10] docs: submitting-patches: Introduce Tested-with: Nikolai Kondrashov
2023-12-05 18:59 ` Jonathan Corbet
2023-12-05 19:07 ` Joe Perches
2023-12-06 10:07 ` Geert Uytterhoeven
2023-12-06 16:46 ` Nikolai Kondrashov
2023-12-06 16:31 ` Nikolai Kondrashov
2023-12-05 18:03 ` [RFC PATCH v2 05/10] checkpatch: Propose tests to execute Nikolai Kondrashov
2023-12-05 18:03 ` [RFC PATCH v2 06/10] MAINTAINERS: Support referencing test docs in V: Nikolai Kondrashov
2023-12-06 8:03 ` David Gow
2023-12-06 16:54 ` Nikolai Kondrashov
2023-12-05 18:03 ` [RFC PATCH v2 07/10] MAINTAINERS: Propose kvm-xfstests smoke for ext4 Nikolai Kondrashov
2023-12-05 18:03 ` [RFC PATCH v2 08/10] docs: tests: Document kunit in general Nikolai Kondrashov
2023-12-05 18:03 ` [RFC PATCH v2 09/10] MAINTAINERS: Propose kunit tests for regmap Nikolai Kondrashov
2023-12-05 18:03 ` [RFC PATCH v2 10/10] MAINTAINERS: Add proposal strength to V: entries Nikolai Kondrashov
2024-01-08 10:42 ` [RFC PATCH v2 00/10] MAINTAINERS: Introduce V: entry for tests Nikolai Kondrashov
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=20231205184503.79769-1-Nikolai.Kondrashov@redhat.com \
--to=nikolai.kondrashov@redhat.com \
--cc=apw@canonical.com \
--cc=broonie@kernel.org \
--cc=cki-project@redhat.com \
--cc=corbet@lwn.net \
--cc=davidgow@google.com \
--cc=djwong@kernel.org \
--cc=joe@perches.com \
--cc=kernelci@lists.linux.dev \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.org \
--cc=tytso@mit.edu \
--cc=vkabatov@redhat.com \
--cc=workflows@vger.kernel.org \
/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