workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: shuah@kernel.org
Cc: Jakub Kicinski <kuba@kernel.org>,
	Tim.Bird@sony.com, linux-kselftest@vger.kernel.org,
	workflows@vger.kernel.org
Subject: [RFC v2] MAINTAINERS: split kselftest entry into 'framework' and 'all'
Date: Fri, 15 Nov 2024 12:09:12 -0800	[thread overview]
Message-ID: <20241115200912.1009680-1-kuba@kernel.org> (raw)

The testing effort is increasing throughout the community.
The tests are generally merged into the subsystem trees,
and are of relatively narrow interest. The patch volume on
linux-kselftest@vger.kernel.org makes it hard to follow
the changes to the framework, and discuss proposals.

Create a new ML focused on the framework of kselftests,
which will hopefully be similarly low volume to the workflows@
mailing list.

From the responses to v1 I gather that the preference is to
keep the existing list for all (or create an alias to it);
the framework-only section should be the one to have a new
list created.

Signed-off-by: Jakub Kicinski <kuba@kernel.org>
---
Sorry for the delay, the responses to v1 weren't super positive
but I keep thinking this would be very useful :) Or at the very
least I find workflows@ very useful and informative as a maintainer.

Posting as an RFC because we need to create the new ML.

v1: https://lore.kernel.org/20241003142328.622730-1-kuba@kernel.org

CC: shuah@kernel.org
CC: Tim.Bird@sony.com
CC: linux-kselftest@vger.kernel.org
CC: workflows@vger.kernel.org
---
 MAINTAINERS | 15 ++++++++++++++-
 1 file changed, 14 insertions(+), 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index f245573722ef..345a0657ba1d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -12395,7 +12395,7 @@ S:	Supported
 F:	Documentation/admin-guide/reporting-regressions.rst
 F:	Documentation/process/handling-regressions.rst
 
-KERNEL SELFTEST FRAMEWORK
+KERNEL SELFTEST
 M:	Shuah Khan <shuah@kernel.org>
 M:	Shuah Khan <skhan@linuxfoundation.org>
 L:	linux-kselftest@vger.kernel.org
@@ -12405,6 +12405,19 @@ T:	git git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git
 F:	Documentation/dev-tools/kselftest*
 F:	tools/testing/selftests/
 
+KERNEL SELFTEST FRAMEWORK
+M:	Shuah Khan <shuah@kernel.org>
+M:	Shuah Khan <skhan@linuxfoundation.org>
+L:	linux-kselftest-core@vger.kernel.org
+S:	Maintained
+F:	Documentation/dev-tools/kselftest*
+F:	tools/testing/selftests/kselftest/
+F:	tools/testing/selftests/lib/
+F:	tools/testing/selftests/lib.mk
+F:	tools/testing/selftests/Makefile
+F:	tools/testing/selftests/*.sh
+F:	tools/testing/selftests/*.h
+
 KERNEL SMB3 SERVER (KSMBD)
 M:	Namjae Jeon <linkinjeon@kernel.org>
 M:	Steve French <sfrench@samba.org>
-- 
2.47.0


             reply	other threads:[~2024-11-15 20:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-15 20:09 Jakub Kicinski [this message]
2024-11-18 21:02 ` Shuah Khan
2024-11-18 21:23   ` Jakub Kicinski
2024-11-22 14:56     ` Shuah
2024-11-22 17:29       ` Jakub Kicinski

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=20241115200912.1009680-1-kuba@kernel.org \
    --to=kuba@kernel.org \
    --cc=Tim.Bird@sony.com \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --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