All of lore.kernel.org
 help / color / mirror / Atom feed
From: asmadeus@codewreck.org
To: Chengming Zhou <chengming.zhou@linux.dev>
Cc: ericvh@kernel.org, lucho@ionkov.net, linux_oss@crudebyte.com,
	v9fs@lists.linux.dev, linux-kernel@vger.kernel.org,
	vbabka@suse.cz, roman.gushchin@linux.dev,
	Xiongwei.Song@windriver.com
Subject: Re: [PATCH] 9p: remove SLAB_MEM_SPREAD flag usage
Date: Mon, 4 Mar 2024 22:10:42 +0900	[thread overview]
Message-ID: <ZeXIUlqnp23qTxo2@codewreck.org> (raw)
In-Reply-To: <2de0d872-0e05-4fbb-8291-0c60487ccd8d@linux.dev>

Chengming Zhou wrote on Mon, Feb 26, 2024 at 10:51:00AM +0800:
> On 2024/2/24 21:46, chengming.zhou@linux.dev wrote:
> > From: Chengming Zhou <zhouchengming@bytedance.com>
> > 
> > The SLAB_MEM_SPREAD flag is already a no-op as of 6.8-rc1, remove
> > its usage so we can delete it from slab. No functional change.
> 
> Update changelog to make it clearer:
> 
> The SLAB_MEM_SPREAD flag used to be implemented in SLAB, which was
> removed as of v6.8-rc1, so it became a dead flag since the commit
> 16a1d968358a ("mm/slab: remove mm/slab.c and slab_def.h"). And the
> series[1] went on to mark it obsolete to avoid confusion for users.
> Here we can just remove all its users, which has no functional change.
> 
> [1] https://lore.kernel.org/all/20240223-slab-cleanup-flags-v2-1-02f1753e8303@suse.cz/

Thanks for the updated text, this is a bit better.
I've updated your commit message with this and will push to Linus next
merge window in a couple of weeks, as you said there's no change so no
reason to submit a patch this late in the cycle.

-- 
Dominique Martinet | Asmadeus

      reply	other threads:[~2024-03-04 13:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-24 13:46 [PATCH] 9p: remove SLAB_MEM_SPREAD flag usage chengming.zhou
2024-02-26  2:51 ` Chengming Zhou
2024-03-04 13:10   ` asmadeus [this message]

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=ZeXIUlqnp23qTxo2@codewreck.org \
    --to=asmadeus@codewreck.org \
    --cc=Xiongwei.Song@windriver.com \
    --cc=chengming.zhou@linux.dev \
    --cc=ericvh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux_oss@crudebyte.com \
    --cc=lucho@ionkov.net \
    --cc=roman.gushchin@linux.dev \
    --cc=v9fs@lists.linux.dev \
    --cc=vbabka@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.