mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Honggyu Kim <honggyu.kim@sk.com>
To: Gregory Price <gourry@gourry.net>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: kernel_team@skhynix.com, Rakie Kim <rakie.kim@sk.com>,
	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,
	yunjeong.mun@sk.com
Subject: Re: [PATCH v5 3/3] mm/mempolicy: Support memory hotplug in weighted interleave
Date: Wed, 2 Apr 2025 14:32:03 +0900	[thread overview]
Message-ID: <62664200-c087-48ed-960f-264f340cf7af@sk.com> (raw)
In-Reply-To: <Z-zIBM4zQ0LbGPYZ@gourry-fedora-PF4VCD3F>

Hi Gregory,

On 4/2/2025 2:15 PM, Gregory Price wrote:
> On Tue, Apr 01, 2025 at 09:34:39PM -0700, Andrew Morton wrote:
>>> I'm not sure if this is going to the final version but could you please add this
>>> patch to stable with Cc: <stable@vger.kernel.org>?
>>> We might need to bring the whole series to avoid conflicts to stable tree.
>>
>> This is all rather confused.
>>
>> Do we need to backport all three patches into -stable?  If so, all three
>> should have Fixes:.  Preferably they all have the same Fixes: so we
>> aren't backporting untested patch combinations.
>>
> 
> I'd just as soon leave the entire thing out of stable backports.
> 
> Only the first patch actually fixes a bug (very small memory leak
> during system tear down, so it's not even a critical bug). This could
> be added to stable.
> 
> Patches 2 and 3 aren't fixes, they're desired behavioral changes
> to the feature. An interface being confusing doesn't mean it's broken.

I think those are fixes but I also agree that this is behavioral changes as
well.  So I'm fine leaving these out of stable backports.


Hi Andrew,

I won't ask changes so please keep the current status as is.  Sorry for making
confusion.

Thanks,
Honggyu

> 
> ~Gregory


  parent reply	other threads:[~2025-04-02  5:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-02  1:49 [PATCH v5 0/3] Enhance sysfs handling for " Rakie Kim
2025-04-02  1:49 ` [PATCH v5 1/3] mm/mempolicy: Fix memory leaks in weighted interleave sysfs Rakie Kim
2025-04-02  1:49 ` [PATCH v5 2/3] mm/mempolicy: Support dynamic sysfs updates for weighted interleave Rakie Kim
2025-04-02  1:49 ` [PATCH v5 3/3] mm/mempolicy: Support memory hotplug in " Rakie Kim
2025-04-02  4:18   ` Honggyu Kim
2025-04-02  4:34     ` Andrew Morton
2025-04-02  5:15       ` Gregory Price
2025-04-02  5:23         ` Gregory Price
2025-04-02  5:32         ` Honggyu Kim [this message]
2025-04-02  9:51   ` Oscar Salvador
2025-04-02 14:14     ` Gregory Price
2025-04-02 15:41       ` Oscar Salvador
2025-04-02 16:36         ` Gregory Price
2025-04-03  4:26           ` Rakie Kim
2025-04-03  5:45             ` Rakie Kim

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=62664200-c087-48ed-960f-264f340cf7af@sk.com \
    --to=honggyu.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=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=rakie.kim@sk.com \
    --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

all inboxes | Powered by JetHome®