From: David Sterba <dsterba@suse.cz>
To: chengming.zhou@linux.dev
Cc: dsterba@suse.com, zhouchengming@bytedance.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, vbabka@suse.cz, roman.gushchin@linux.dev,
Xiongwei.Song@windriver.com
Subject: Re: [PATCH] affs: remove SLAB_MEM_SPREAD flag usage
Date: Mon, 26 Feb 2024 11:33:20 +0100 [thread overview]
Message-ID: <20240226103320.GR355@suse.cz> (raw)
In-Reply-To: <20240224134637.829075-1-chengming.zhou@linux.dev>
On Sat, Feb 24, 2024 at 01:46:37PM +0000, 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.
>
> Signed-off-by: Chengming Zhou <zhouchengming@bytedance.com>
Thanks, I'll pick it for the next merge window.
prev parent reply other threads:[~2024-02-26 10:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 13:46 [PATCH] affs: remove SLAB_MEM_SPREAD flag usage chengming.zhou
2024-02-26 10:33 ` David Sterba [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=20240226103320.GR355@suse.cz \
--to=dsterba@suse.cz \
--cc=Xiongwei.Song@windriver.com \
--cc=chengming.zhou@linux.dev \
--cc=dsterba@suse.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=roman.gushchin@linux.dev \
--cc=vbabka@suse.cz \
--cc=zhouchengming@bytedance.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).