[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250417153505.c921f75a035089906bb38fe6@linux-foundation.org>
Date: Thu, 17 Apr 2025 15:35:05 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Rakie Kim <rakie.kim@...com>
Cc: gourry@...rry.net, linux-mm@...ck.org, linux-kernel@...r.kernel.org,
linux-cxl@...r.kernel.org, joshua.hahnjy@...il.com,
dan.j.williams@...el.com, ying.huang@...ux.alibaba.com, david@...hat.com,
Jonathan.Cameron@...wei.com, osalvador@...e.de, kernel_team@...ynix.com,
honggyu.kim@...com, yunjeong.mun@...com
Subject: Re: [PATCH v9 0/3] Enhance sysfs handling for memory hotplug in
weighted interleave
On Thu, 17 Apr 2025 17:10:08 +0900 Rakie Kim <rakie.kim@...com> wrote:
> 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.
No probs, this is why mm.git workflow (mm-new -> mm-unstable ->
mm-stable -> mainline) operates as it does - to easily permit revisions
and replacements as patches move towards their final state.
Please note that I added a cc:stable to your [1/N] patch - sysfs leaks
should be fixed in earlier kernels. I considered this to be low
priority - if it's higher priority than this patch should best have
been separated from the series, so it can take a different merge path
from the other patches.
Powered by blists - more mailing lists