All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Justin Stitt <justinstitt@google.com>
Cc: linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Nathan Chancellor <nathan@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	geert@linux-m68k.org, gregkh@linuxfoundation.org,
	workflows@vger.kernel.org, mario.limonciello@amd.com
Subject: Re: [PATCH v2 2/2] MAINTAINERS: migrate some K to D
Date: Wed, 27 Sep 2023 21:49:46 -0700	[thread overview]
Message-ID: <296cf67699ab7aefe378b6719230a50e2851fe7b.camel@perches.com> (raw)
In-Reply-To: <20230928-get_maintainer_add_d-v2-2-8acb3f394571@google.com>

On Thu, 2023-09-28 at 04:23 +0000, Justin Stitt wrote:
> Let's get the ball rolling with some changes from K to D.
> 
> Ultimately, if it turns out that 100% of K users want to change to D
> then really the behavior of K could just be changed.

Given my suggestion to 1/2, this would be unnecessary.

> 
> Signed-off-by: Justin Stitt <justinstitt@google.com>
> Original-author: Kees Cook <keescook@chromium.org>
> ---
>  MAINTAINERS | 16 +++++++++-------
>  1 file changed, 9 insertions(+), 7 deletions(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 94e431daa7c2..80ffdaa8f044 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -5038,7 +5038,7 @@ F:	Documentation/kbuild/llvm.rst
>  F:	include/linux/compiler-clang.h
>  F:	scripts/Makefile.clang
>  F:	scripts/clang-tools/
> -K:	\b(?i:clang|llvm)\b
> +D:	\b(?i:clang|llvm)\b
>  
>  CLK API
>  M:	Russell King <linux@armlinux.org.uk>
> @@ -8149,7 +8149,7 @@ F:	lib/strcat_kunit.c
>  F:	lib/strscpy_kunit.c
>  F:	lib/test_fortify/*
>  F:	scripts/test_fortify.sh
> -K:	\b__NO_FORTIFY\b
> +D:	\b__NO_FORTIFY\b
>  
>  FPGA DFL DRIVERS
>  M:	Wu Hao <hao.wu@intel.com>
> @@ -11405,8 +11405,10 @@ F:	Documentation/ABI/testing/sysfs-kernel-warn_count
>  F:	include/linux/overflow.h
>  F:	include/linux/randomize_kstack.h
>  F:	mm/usercopy.c
> -K:	\b(add|choose)_random_kstack_offset\b
> -K:	\b__check_(object_size|heap_object)\b
> +D:	\b(add|choose)_random_kstack_offset\b
> +D:	\b__check_(object_size|heap_object)\b
> +D:	\b__counted_by\b
> +
>  
>  KERNEL JANITORS
>  L:	kernel-janitors@vger.kernel.org
> @@ -17290,7 +17292,7 @@ F:	drivers/acpi/apei/erst.c
>  F:	drivers/firmware/efi/efi-pstore.c
>  F:	fs/pstore/
>  F:	include/linux/pstore*
> -K:	\b(pstore|ramoops)
> +D:	\b(pstore|ramoops)
>  
>  PTP HARDWARE CLOCK SUPPORT
>  M:	Richard Cochran <richardcochran@gmail.com>
> @@ -19231,8 +19233,8 @@ F:	include/uapi/linux/seccomp.h
>  F:	kernel/seccomp.c
>  F:	tools/testing/selftests/kselftest_harness.h
>  F:	tools/testing/selftests/seccomp/*
> -K:	\bsecure_computing
> -K:	\bTIF_SECCOMP\b
> +D:	\bsecure_computing
> +D:	\bTIF_SECCOMP\b
>  
>  SECURE DIGITAL HOST CONTROLLER INTERFACE (SDHCI) Broadcom BRCMSTB DRIVER
>  M:	Kamal Dasu <kamal.dasu@broadcom.com>
> 


  reply	other threads:[~2023-09-28  4:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-28  4:23 [PATCH v2 0/2] get_maintainer: add patch-only keyword matching Justin Stitt
2023-09-28  4:23 ` [PATCH v2 1/2] get_maintainer: add patch-only keyword-matching Justin Stitt
2023-09-28  4:46   ` Joe Perches
2023-09-28  5:03     ` Justin Stitt
2023-09-28  5:08       ` Joe Perches
2023-09-28 19:12         ` Konstantin Ryabitsev
2023-09-28  4:23 ` [PATCH v2 2/2] MAINTAINERS: migrate some K to D Justin Stitt
2023-09-28  4:49   ` Joe Perches [this message]
2023-09-28  5:01 ` [PATCH v2 0/2] get_maintainer: add patch-only keyword matching Joe Perches
2023-09-28  5:31   ` Justin Stitt
2023-09-28  6:09     ` Joe Perches
2023-09-28 15:52       ` Nick Desaulniers
2023-09-29  2:07         ` Justin Stitt
2023-09-29  2:50           ` Joe Perches
2023-09-29  3:07             ` Justin Stitt

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=296cf67699ab7aefe378b6719230a50e2851fe7b.camel@perches.com \
    --to=joe@perches.com \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=justinstitt@google.com \
    --cc=keescook@chromium.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.