From: Sang-Heon Jeon <ekffu200098@gmail.com>
To: akpm@linux-foundation.org, rppt@kernel.org, djbw@kernel.org,
mingo@kernel.org
Cc: linux-mm@kvack.org, Sang-Heon Jeon <ekffu200098@gmail.com>
Subject: [RFC PATCH 0/2] mm/fake-numa: fix under-allocation detection logic in uniform split
Date: Tue, 14 Apr 2026 00:44:36 +0900 [thread overview]
Message-ID: <20260413154438.396031-1-ekffu200098@gmail.com> (raw)
Hello,
This series fixes under-allocation detection logic and an outdated
comment in uniform NUMA node splitting.
I found this while going through NUMA enulation codes. If I
misunderstood, feel free to tell me about it.
Thank you for taking your valuable time to review this work.
Best Regards,
Sang-Heon Jeon
Sang-Heon Jeon (2):
mm/fake-numa: fix under-allocation detection in uniform split
mm/fake-numa: fix outdated return value comment
mm/numa_emulation.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--
2.43.0
next reply other threads:[~2026-04-13 15:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 15:44 Sang-Heon Jeon [this message]
2026-04-13 15:44 ` [RFC PATCH 1/2] " Sang-Heon Jeon
2026-04-13 15:44 ` [RFC PATCH 2/2] mm/fake-numa: fix outdated return value comment Sang-Heon Jeon
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=20260413154438.396031-1-ekffu200098@gmail.com \
--to=ekffu200098@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=djbw@kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@kernel.org \
--cc=rppt@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