From: Mike Rapoport <rppt@kernel.org>
To: Suren Baghdasaryan <surenb@google.com>
Cc: akpm@linux-foundation.org, kent.overstreet@linux.dev,
david@kernel.org, ljs@kernel.org, liam@infradead.org,
vbabka@kernel.org, hao.ge@linux.dev, jackmanb@google.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 2/2] mm: move alloc tag to mm
Date: Fri, 26 Jun 2026 12:17:35 +0300 [thread overview]
Message-ID: <aj5Dr99W4we3BSLS@kernel.org> (raw)
In-Reply-To: <20260625184857.2193482-3-surenb@google.com>
On Thu, Jun 25, 2026 at 11:48:57AM -0700, Suren Baghdasaryan wrote:
> From: Lorenzo Stoakes <ljs@kernel.org>
>
> The alloc tagging work is really mm-specific, so move alloc_tag.c to mm/
> and additionally update the MAINTAINERS entry to place it within memory
> management and port over the Kconfig and Makefile code to mm.
>
> Signed-off-by: Lorenzo Stoakes <ljs@kernel.org>
> Signed-off-by: Suren Baghdasaryan <surenb@google.com>
Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> ---
> MAINTAINERS | 20 ++++++++++----------
> lib/Kconfig.debug | 28 ----------------------------
> lib/Makefile | 1 -
> mm/Kconfig.debug | 28 ++++++++++++++++++++++++++++
> mm/Makefile | 1 +
> {lib => mm}/alloc_tag.c | 0
> 6 files changed, 39 insertions(+), 39 deletions(-)
> rename {lib => mm}/alloc_tag.c (100%)
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2026-06-26 9:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 18:48 [PATCH 0/2] move alloc_tag.c file under mm/ Suren Baghdasaryan
2026-06-25 18:48 ` [PATCH 1/2] MAINTAINERS: move inactive maintainer to CREDITS Suren Baghdasaryan
2026-06-26 10:13 ` Lorenzo Stoakes
2026-06-25 18:48 ` [PATCH 2/2] mm: move alloc tag to mm Suren Baghdasaryan
2026-06-25 23:56 ` SeongJae Park
2026-06-26 2:24 ` Hao Ge
2026-06-26 9:12 ` Vlastimil Babka (SUSE)
2026-06-26 9:13 ` David Hildenbrand (Arm)
2026-06-26 9:17 ` Mike Rapoport [this message]
2026-06-26 9:26 ` Harry Yoo
2026-06-26 10:12 ` Lorenzo Stoakes
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=aj5Dr99W4we3BSLS@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=hao.ge@linux.dev \
--cc=jackmanb@google.com \
--cc=kent.overstreet@linux.dev \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@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.