linux-kernel - Re: [PATCH] MAINTAINERS: Update Kselftest Framework mailing list

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87mvqyrwj4.fsf@kamboji.qca.qualcomm.com>
Date:	Thu, 18 Feb 2016 15:13:51 +0200
From:	Kalle Valo <kvalo@...eaurora.org>
To:	Shuah Khan <shuahkh@....samsung.com>
Cc:	akpm@...ux-foundation.org, gregkh@...uxfoundation.org,
	davem@...emloft.net, mchehab@....samsung.com, joe@...ches.com,
	jslaby@...e.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Update Kselftest Framework mailing list

Shuah Khan <shuahkh@....samsung.com> writes:

> Kselftest Framework now has a dedicated mailing list
> linux-kselftest. Update the entry in MAINTAINERS file.
>
> Signed-off-by: Shuah Khan <shuahkh@....samsung.com>
> ---
>  MAINTAINERS | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index cc2f753..e3acba8 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -6128,7 +6128,7 @@ F:	include/uapi/linux/sunrpc/
>  
>  KERNEL SELFTEST FRAMEWORK
>  M:	Shuah Khan <shuahkh@....samsung.com>
> -L:	linux-api@...r.kernel.org
> +L:	linux-kselftest@...r.kernel.org
>  T:	git git://git.kernel.org/pub/scm/shuah/linux-kselftest
>  S:	Maintained
>  F:	tools/testing/selftests

Just out of curiosity, but why did you decide to CC me? Lately I have
been CCed in unrelated patches without any apparent reason (or at least
that's how it looks like to me). I'm starting to wonder if there's a
buggy script or something?

Now that I think this more, is it actually because I did quite a few
changes to MAINTAINERS file due to the recent wireless drivers mass
move?

-- 
Kalle Valo