From: Shuah Khan <skhan@linuxfoundation.org>
To: Jakub Kicinski <kuba@kernel.org>, shuah@kernel.org
Cc: Tim.Bird@sony.com, linux-kselftest@vger.kernel.org,
workflows@vger.kernel.org, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [RFC v2] MAINTAINERS: split kselftest entry into 'framework' and 'all'
Date: Mon, 18 Nov 2024 14:02:29 -0700 [thread overview]
Message-ID: <8192e307-b2b9-4c48-87e2-31073c084218@linuxfoundation.org> (raw)
In-Reply-To: <20241115200912.1009680-1-kuba@kernel.org>
On 11/15/24 13:09, Jakub Kicinski wrote:
> 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.
I have to repeat the same thing I said when you sent RFC v1
It is going to add the confusion - people don't cc the one mailing list
we have now.
I am going to have to say no. Sorry.
thanks,
-- Shuah
next prev parent reply other threads:[~2024-11-18 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 20:09 Jakub Kicinski
2024-11-18 21:02 ` Shuah Khan [this message]
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=8192e307-b2b9-4c48-87e2-31073c084218@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=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