[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240221120030.GI355@twin.jikos.cz>
Date: Wed, 21 Feb 2024 13:00:30 +0100
From: David Sterba <dsterba@...e.cz>
To: Kunwu Chan <chentao@...inos.cn>
Cc: clm@...com, josef@...icpanda.com, dsterba@...e.com,
linux-btrfs@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/6] btrfs: Use KMEM_CACHE instead of kmem_cache_create
On Tue, Feb 20, 2024 at 05:06:39PM +0800, Kunwu Chan wrote:
> As David Sterba said in
> https://lore.kernel.org/all/20240205160408.GI355@twin.jikos.cz/
> I'm using a patchset to cleanup the same issues in the 'brtfs' module.
>
> For where the cache name and the structure name match.
> Use the new KMEM_CACHE() macro instead of direct kmem_cache_create
> to simplify the creation of SLAB caches.
>
> Kunwu Chan (6):
> btrfs: Simplify the allocation of slab caches in
> btrfs_delayed_inode_init
> btrfs: Simplify the allocation of slab caches in ordered_data_init
> btrfs: Simplify the allocation of slab caches in
> btrfs_transaction_init
> btrfs: Simplify the allocation of slab caches in btrfs_ctree_init
> btrfs: Simplify the allocation of slab caches in
> btrfs_delayed_ref_init
> btrfs: Simplify the allocation of slab caches in btrfs_free_space_init
Added to for-next, thanks. I've edited the changels so the name of the
structure is mentioned rather than the function where it happens, and
did some minor formatting adjustments.
Powered by blists - more mailing lists