From: Rakie Kim <rakie.kim@sk.com>
To: akpm@linux-foundation.org
Cc: gourry@gourry.net, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, linux-cxl@vger.kernel.org,
joshua.hahnjy@gmail.com, dan.j.williams@intel.com,
ying.huang@linux.alibaba.com, david@redhat.com,
Jonathan.Cameron@huawei.com, osalvador@suse.de,
kernel_team@skhynix.com, honggyu.kim@sk.com, yunjeong.mun@sk.com,
rakie.kim@sk.com
Subject: Re: [PATCH v9 0/3] Enhance sysfs handling for memory hotplug in weighted interleave
Date: Thu, 17 Apr 2025 17:10:08 +0900 [thread overview]
Message-ID: <20250417081106.732-1-rakie.kim@sk.com> (raw)
In-Reply-To: <20250417072839.711-1-rakie.kim@sk.com>
On Thu, 17 Apr 2025 16:28:34 +0900 Rakie Kim <rakie.kim@sk.com> wrote:
> These patches have been tested under CXL-based memory configurations,
> including hotplug scenarios, to ensure proper behavior and stability.
>
> mm/mempolicy.c | 240 ++++++++++++++++++++++++++++++-------------------
> 1 file changed, 148 insertions(+), 92 deletions(-)
>
> base-commit: 8ffd015db85fea3e15a77027fda6c02ced4d2444
> --
To Andrew
I sincerely apologize for causing repeated inconvenience. The series of
patches version v8 that was merged into -mm, mm-new today needs
additional corrections.
Link: https://lore.kernel.org/all/6800742de6315_130fd2949c@dwillia2-mobl3.amr.corp.intel.com.notmuch/
Therefore, I have updated a new version v9, in which the problems have
been addressed.
I would greatly appreciate it if you could drop the existing v8 and
replace it with the new version v9. Below is the information regarding
the v8 patch series that needs to be dropped.
Once again, I truly apologize for the inconvenience.
<1>
The patch titled:
Subject: mm/mempolicy: fix memory leaks in weighted interleave sysfs
Filename:
mm-mempolicy-fix-memory-leaks-in-weighted-interleave-sysfs.patch
<2>
The patch titled:
Subject: mm/mempolicy: prepare weighted interleave sysfs for memory hotplug
Filename:
mm-mempolicy-prepare-weighted-interleave-sysfs-for-memory-hotplug.patch
<3>
The patch titled:
Subject: mm/mempolicy: support memory hotplug in weighted interleave
Filename:
mm-mempolicy-support-memory-hotplug-in-weighted-interleave.patch
Rakie
next prev parent reply other threads:[~2025-04-17 8:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 7:28 Rakie Kim
2025-04-17 7:28 ` [PATCH v9 1/3] mm/mempolicy: Fix memory leaks in weighted interleave sysfs Rakie Kim
2025-04-17 7:28 ` [PATCH v9 2/3] mm/mempolicy: Prepare weighted interleave sysfs for memory hotplug Rakie Kim
2025-04-17 7:28 ` [PATCH v9 3/3] mm/mempolicy: Support memory hotplug in weighted interleave Rakie Kim
2025-04-17 8:10 ` Rakie Kim [this message]
2025-04-17 22:35 ` [PATCH v9 0/3] Enhance sysfs handling for " Andrew Morton
2025-04-17 22:41 ` Dan Williams
2025-04-17 23:31 ` Andrew Morton
2025-04-17 22:56 ` Dan Williams
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=20250417081106.732-1-rakie.kim@sk.com \
--to=rakie.kim@sk.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=gourry@gourry.net \
--cc=honggyu.kim@sk.com \
--cc=joshua.hahnjy@gmail.com \
--cc=kernel_team@skhynix.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=ying.huang@linux.alibaba.com \
--cc=yunjeong.mun@sk.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