From: "Bird, Tim" <Tim.Bird@sony.com>
To: Jakub Kicinski <kuba@kernel.org>, "shuah@kernel.org" <shuah@kernel.org>
Cc: "linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>,
"workflows@vger.kernel.org" <workflows@vger.kernel.org>
Subject: RE: [RFC] MAINTAINERS: split kselftest entry into 'framework' and 'all'
Date: Thu, 3 Oct 2024 15:05:06 +0000 [thread overview]
Message-ID: <MW5PR13MB5632FECA88BE3F0711032738FD712@MW5PR13MB5632.namprd13.prod.outlook.com> (raw)
In-Reply-To: <20241003142328.622730-1-kuba@kernel.org>
> -----Original Message-----
> From: Jakub Kicinski <kuba@kernel.org>
> 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 for "all" of kselftests (tests and framework),
> replacing the old list. Use the old list for framework changes
> only. It would cause less churn to create a ML for just the
> framework, but I prefer to use the shorter name for the list
> which has much more practical use.
I'm not a fan of this split.
The approach taken seems like it would create a lot of churn.
You have 2 kinds of developers - a) developers of the framework
and b) developers of the tests themselves. Are you trying to shield
framework developers from discussions about tests, or test developers
from discussions about the framework? It seems like framework developers
would be interested in seeing discussions about tests, and vice-versa.
I'm not sure a new list is needed, but if the discussion needs to be split,
I think it would be better to create a new list for framework-only
discussions, and leave the old list handling all (both framework and tests).
Like maybe have the new list be something like "linux-kselftest-core@vger.kernel.org"?
-- Tim
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> Posting as an RFC because we need to create the new ML.
>
> CC: shuah@kernel.org
> CC: linux-kselftest@vger.kernel.org
> CC: workflows@vger.kernel.org
> ---
> MAINTAINERS | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index c27f3190737f..9a03dc1c8974 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -12401,6 +12401,18 @@ S: Maintained
> Q: https://patchwork.kernel.org/project/linux-kselftest/list/
> T: git git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git
> 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 SELFTEST TESTS
> +M: Shuah Khan <shuah@kernel.org>
> +M: Shuah Khan <skhan@linuxfoundation.org>
> +L: linux-kselftest-all@vger.kernel.org
> +S: Maintained
> F: tools/testing/selftests/
>
> KERNEL SMB3 SERVER (KSMBD)
> --
> 2.46.2
>
next prev parent reply other threads:[~2024-10-03 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 14:23 Jakub Kicinski
2024-10-03 15:05 ` Bird, Tim [this message]
2024-10-03 16:02 ` Jakub Kicinski
2024-10-03 20:44 ` Shuah
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=MW5PR13MB5632FECA88BE3F0711032738FD712@MW5PR13MB5632.namprd13.prod.outlook.com \
--to=tim.bird@sony.com \
--cc=kuba@kernel.org \
--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