From: Christian Brauner <brauner@kernel.org>
To: jlayton@kernel.org, jack@suse.cz, zhouchengming@bytedance.com,
akpm@linux-foundation.org, willy@infradead.org,
chengming.zhou@linux.dev
Cc: Christian Brauner <brauner@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] minix: remove SLAB_MEM_SPREAD flag usage
Date: Tue, 27 Feb 2024 11:52:46 +0100 [thread overview]
Message-ID: <20240227-liege-gasheizung-15d8684aae8e@brauner> (raw)
In-Reply-To: <20240224134935.829715-1-chengming.zhou@linux.dev>
On Sat, 24 Feb 2024 13:49:35 +0000, chengming.zhou@linux.dev wrote:
> 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.
>
>
Updated commit message to point to slab removal.
---
Applied to the vfs.misc branch of the vfs/vfs.git tree.
Patches in the vfs.misc branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.misc
[1/1] minix: remove SLAB_MEM_SPREAD flag usage
https://git.kernel.org/vfs/vfs/c/84a9fad0729b
prev parent reply other threads:[~2024-02-27 10:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 13:49 [PATCH] minix: remove SLAB_MEM_SPREAD flag usage chengming.zhou
2024-02-27 10:52 ` Christian Brauner [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=20240227-liege-gasheizung-15d8684aae8e@brauner \
--to=brauner@kernel.org \
--cc=Xiongwei.Song@windriver.com \
--cc=akpm@linux-foundation.org \
--cc=chengming.zhou@linux.dev \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=roman.gushchin@linux.dev \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--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 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.