From: Suren Baghdasaryan <surenb@google.com>
To: akpm@linux-foundation.org
Cc: kent.overstreet@linux.dev, david@kernel.org, ljs@kernel.org,
liam@infradead.org, vbabka@kernel.org, rppt@kernel.org,
hao.ge@linux.dev, jackmanb@google.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
surenb@google.com
Subject: [PATCH 0/2] move alloc_tag.c file under mm/
Date: Thu, 25 Jun 2026 11:48:55 -0700 [thread overview]
Message-ID: <20260625184857.2193482-1-surenb@google.com> (raw)
Memory allocation profiling is ultimately an mm feature and now that we
need to use some internal mm definitions in it [1], the time is right to
move its implementation under mm/. The move is straight-forward, involving
just alloc_tag.c file. Update config, makefiles and maintainers as well.
[1] https://lore.kernel.org/all/20260622-alloc-trylock-v2-13-31f31367d420@google.com/
Lorenzo Stoakes (1):
mm: move alloc tag to mm
Suren Baghdasaryan (1):
MAINTAINERS: move inactive maintainer to CREDITS
CREDITS | 4 ++++
MAINTAINERS | 21 ++++++++++-----------
lib/Kconfig.debug | 28 ----------------------------
lib/Makefile | 1 -
mm/Kconfig.debug | 28 ++++++++++++++++++++++++++++
mm/Makefile | 1 +
{lib => mm}/alloc_tag.c | 0
7 files changed, 43 insertions(+), 40 deletions(-)
rename {lib => mm}/alloc_tag.c (100%)
base-commit: 81652c5a65d4ae28e9b18c16ef917a40025c3653
--
2.55.0.rc0.799.gd6f94ed593-goog
next reply other threads:[~2026-06-25 18:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 18:48 Suren Baghdasaryan [this message]
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
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=20260625184857.2193482-1-surenb@google.com \
--to=surenb@google.com \
--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=rppt@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox