From: Christian Brauner <brauner@kernel.org>
To: Kunwu Chan <chentao@kylinos.cn>
Cc: Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-unionfs@vger.kernel.org,
linux-kernel@vger.kernel.org, miklos@szeredi.hu,
amir73il@gmail.com, viro@zeniv.linux.org.uk, jack@suse.cz
Subject: Re: [PATCH] fs: Use KMEM_CACHE instead of kmem_cache_create
Date: Wed, 31 Jan 2024 14:39:13 +0100 [thread overview]
Message-ID: <20240131-kanufahren-lernmittel-ef0624c0aa47@brauner> (raw)
In-Reply-To: <20240131070941.135178-1-chentao@kylinos.cn>
On Wed, 31 Jan 2024 15:09:41 +0800, Kunwu Chan wrote:
> commit 0a31bd5f2bbb ("KMEM_CACHE(): simplify slab cache creation")
> introduces a new macro.
> Use the new KMEM_CACHE() macro instead of direct kmem_cache_create
> to simplify the creation of SLAB caches.
>
>
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] fs: Use KMEM_CACHE instead of kmem_cache_create
https://git.kernel.org/vfs/vfs/c/6f351af0c85f
prev parent reply other threads:[~2024-01-31 13:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 7:09 [PATCH] fs: Use KMEM_CACHE instead of kmem_cache_create Kunwu Chan
2024-01-31 11:18 ` Jan Kara
2024-01-31 13:39 ` 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=20240131-kanufahren-lernmittel-ef0624c0aa47@brauner \
--to=brauner@kernel.org \
--cc=amir73il@gmail.com \
--cc=chentao@kylinos.cn \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=viro@zeniv.linux.org.uk \
/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.