linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Xiongwei Song <xiongwei.song@windriver.com>
Cc: longman@redhat.com, lizefan.x@bytedance.com, hannes@cmpxchg.org,
	corbet@lwn.net, vbabka@suse.cz, yosryahmed@google.com,
	rostedt@goodmis.org, cl@linux.com, chengming.zhou@linux.dev,
	zhengyejian1@huawei.com, cgroups@vger.kernel.org,
	linux-mmc@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] cgroup/cpuset: Remove cpuset_do_slab_mem_spread()
Date: Thu, 29 Feb 2024 10:28:45 -1000	[thread overview]
Message-ID: <ZeDo_U5j7N7sH_v0@slm.duckdns.org> (raw)
In-Reply-To: <20240229142007.1278610-1-xiongwei.song@windriver.com>

On Thu, Feb 29, 2024 at 10:20:06PM +0800, Xiongwei Song wrote:
> The SLAB allocator has been removed sine 6.8-rc1 [1], so there is no user
> with SLAB_MEM_SPREAD and cpuset_do_slab_mem_spread(). Then SLAB_MEM_SPREAD
> is marked as unused by [2]. Here we can remove
> cpuset_do_slab_mem_spread(). For more details, please check [3].
> 
> [1] https://lore.kernel.org/linux-mm/20231120-slab-remove-slab-v2-0-9c9c70177183@suse.cz/
> [2] https://lore.kernel.org/linux-kernel/20240223-slab-cleanup-flags-v2-0-02f1753e8303@suse.cz/T/
> [3] https://lore.kernel.org/lkml/32bc1403-49da-445a-8c00-9686a3b0d6a3@redhat.com/T/#mf14b838c5e0e77f4756d436bac3d8c0447ea4350
> 
> Signed-off-by: Xiongwei Song <xiongwei.song@windriver.com>

Applied to cgroup/for-6.9.

Thanks.

-- 
tejun

      parent reply	other threads:[~2024-02-29 20:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29 14:20 [PATCH 1/2] cgroup/cpuset: Remove cpuset_do_slab_mem_spread() Xiongwei Song
2024-02-29 14:20 ` [PATCH 2/2] cgroup/cpuset: Mark memory_spread_slab as obsolete Xiongwei Song
2024-02-29 14:30   ` Waiman Long
2024-02-29 20:29   ` Tejun Heo
2024-02-29 14:29 ` [PATCH 1/2] cgroup/cpuset: Remove cpuset_do_slab_mem_spread() Waiman Long
2024-02-29 20:28 ` Tejun Heo [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=ZeDo_U5j7N7sH_v0@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=chengming.zhou@linux.dev \
    --cc=cl@linux.com \
    --cc=corbet@lwn.net \
    --cc=hannes@cmpxchg.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=lizefan.x@bytedance.com \
    --cc=longman@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=vbabka@suse.cz \
    --cc=xiongwei.song@windriver.com \
    --cc=yosryahmed@google.com \
    --cc=zhengyejian1@huawei.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;
as well as URLs for NNTP newsgroup(s).