public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <josef@toxicpanda.com>
To: Gaosheng Cui <cuigaosheng1@huawei.com>
Cc: clm@fb.com, dsterba@suse.com, chris.mason@oracle.com,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] btrfs: remove btrfs_bit_radix_cachep declaration
Date: Fri, 9 Sep 2022 08:45:14 -0400	[thread overview]
Message-ID: <Yxs1WpoG9q4R0EGv@localhost.localdomain> (raw)
In-Reply-To: <20220909065451.1155969-1-cuigaosheng1@huawei.com>

On Fri, Sep 09, 2022 at 02:54:51PM +0800, Gaosheng Cui wrote:
> btrfs_bit_radix_cachep has been removed since
> commit 45c06543afe2 ("Btrfs: remove unused btrfs_bit_radix slab"),
> so remove it.
> 
> Signed-off-by: Gaosheng Cui <cuigaosheng1@huawei.com>

Reviewed-by: Josef Bacik <josef@toxicpanda.com>

Thanks,

Josef

      reply	other threads:[~2022-09-09 12:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09  6:54 [PATCH] btrfs: remove btrfs_bit_radix_cachep declaration Gaosheng Cui
2022-09-09 12:45 ` Josef Bacik [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=Yxs1WpoG9q4R0EGv@localhost.localdomain \
    --to=josef@toxicpanda.com \
    --cc=chris.mason@oracle.com \
    --cc=clm@fb.com \
    --cc=cuigaosheng1@huawei.com \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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