From: Kent Overstreet <kent.overstreet@linux.dev>
To: Lukas Bulwahn <lbulwahn@redhat.com>
Cc: Suren Baghdasaryan <surenb@google.com>,
Kees Cook <keescook@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org,
Lukas Bulwahn <lukas.bulwahn@redhat.com>
Subject: Re: [PATCH] MAINTAINERS: improve entries in CODE TAGGING and MEMORY ALLOCATION PROFILING
Date: Thu, 11 Apr 2024 02:58:30 -0400 [thread overview]
Message-ID: <mya4xkisx6bah3dl7znb3uymtpwmqt5mesydr4q2icz2xcyrb3@kx7h4tqdzep5> (raw)
In-Reply-To: <20240411064717.51140-1-lukas.bulwahn@redhat.com>
On Thu, Apr 11, 2024 at 08:47:17AM +0200, Lukas Bulwahn wrote:
> Commit 5acf2502db99 ("MAINTAINERS: add entries for code tagging and memory
> allocation profiling") adds the two new sections CODE TAGGING and MEMORY
> ALLOCATION PROFILING. The files in these sections however do not match
> with the files added in the corresponding patch series.
>
> Improve the two entries to refer to all files added with that series and
> drop the entries to non-existing files.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@redhat.com>
Acked-by: Kent Overstreet <kent.overstreet@linux.dev>
> ---
> MAINTAINERS | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index c2d913c64704..e5431f06ab55 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -5332,6 +5332,7 @@ CODE TAGGING
> M: Suren Baghdasaryan <surenb@google.com>
> M: Kent Overstreet <kent.overstreet@linux.dev>
> S: Maintained
> +F: include/asm-generic/codetag.lds.h
> F: include/linux/codetag.h
> F: lib/codetag.c
>
> @@ -14241,10 +14242,10 @@ M: Suren Baghdasaryan <surenb@google.com>
> M: Kent Overstreet <kent.overstreet@linux.dev>
> L: linux-mm@kvack.org
> S: Maintained
> +F: Documentation/mm/allocation-profiling.rst
> F: include/linux/alloc_tag.h
> -F: include/linux/codetag_ctx.h
> +F: include/linux/pgalloc_tag.h
> F: lib/alloc_tag.c
> -F: lib/pgalloc_tag.c
>
> MEMORY CONTROLLER DRIVERS
> M: Krzysztof Kozlowski <krzk@kernel.org>
> --
> 2.44.0
>
prev parent reply other threads:[~2024-04-11 6:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 6:47 Lukas Bulwahn
2024-04-11 6:58 ` Kent Overstreet [this message]
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=mya4xkisx6bah3dl7znb3uymtpwmqt5mesydr4q2icz2xcyrb3@kx7h4tqdzep5 \
--to=kent.overstreet@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=keescook@chromium.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=lbulwahn@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lukas.bulwahn@redhat.com \
--cc=surenb@google.com \
/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