From: Anand Jain <anand.jain@oracle.com>
To: Goldwyn Rodrigues <rgoldwyn@suse.de>, linux-btrfs@vger.kernel.org
Cc: Goldwyn Rodrigues <rgoldwyn@suse.com>
Subject: Re: [PATCH 1/2] btrfs: Remove unused function btrfs_reada_detach()
Date: Wed, 7 Apr 2021 07:59:26 +0800 [thread overview]
Message-ID: <2bce898b-bb2b-cedb-1b09-cecd48b5e73d@oracle.com> (raw)
In-Reply-To: <20210406162404.11746-1-rgoldwyn@suse.de>
On 07/04/2021 00:24, Goldwyn Rodrigues wrote:
> From: Goldwyn Rodrigues <rgoldwyn@suse.com>
>
> btrfs_reada_detach() is not called by any function. Remove.
>
btrfs_reada_detach() was never used.
commit 48a3b6366f69 (btrfs: make static code static & remove dead code)
spared it.
IMO ok to remove btrfs_reada_detach().
Reviewed-by: Anand Jain <anand.jain@oracle.com>
> Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.com>
> ---
> fs/btrfs/ctree.h | 1 -
> fs/btrfs/reada.c | 9 +--------
> 2 files changed, 1 insertion(+), 9 deletions(-)
>
> diff --git a/fs/btrfs/ctree.h b/fs/btrfs/ctree.h
> index f2fd73e58ee6..2acbd8919611 100644
> --- a/fs/btrfs/ctree.h
> +++ b/fs/btrfs/ctree.h
> @@ -3700,7 +3700,6 @@ struct reada_control {
> struct reada_control *btrfs_reada_add(struct btrfs_root *root,
> struct btrfs_key *start, struct btrfs_key *end);
> int btrfs_reada_wait(void *handle);
> -void btrfs_reada_detach(void *handle);
> int btree_readahead_hook(struct extent_buffer *eb, int err);
> void btrfs_reada_remove_dev(struct btrfs_device *dev);
> void btrfs_reada_undo_remove_dev(struct btrfs_device *dev);
> diff --git a/fs/btrfs/reada.c b/fs/btrfs/reada.c
> index 06713a8fe26b..0d357f8b65bc 100644
> --- a/fs/btrfs/reada.c
> +++ b/fs/btrfs/reada.c
> @@ -24,7 +24,7 @@
> * To trigger a readahead, btrfs_reada_add must be called. It will start
> * a read ahead for the given range [start, end) on tree root. The returned
> * handle can either be used to wait on the readahead to finish
> - * (btrfs_reada_wait), or to send it to the background (btrfs_reada_detach).
> + * (btrfs_reada_wait).
> *
> * The read ahead works as follows:
> * On btrfs_reada_add, the root of the tree is inserted into a radix_tree.
> @@ -1036,13 +1036,6 @@ int btrfs_reada_wait(void *handle)
> }
> #endif
>
> -void btrfs_reada_detach(void *handle)
> -{
> - struct reada_control *rc = handle;
> -
> - kref_put(&rc->refcnt, reada_control_release);
> -}
> -
> /*
> * Before removing a device (device replace or device remove ioctls), call this
> * function to wait for all existing readahead requests on the device and to
>
next prev parent reply other threads:[~2021-04-06 23:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 16:24 [PATCH 1/2] btrfs: Remove unused function btrfs_reada_detach() Goldwyn Rodrigues
2021-04-06 16:24 ` [PATCH 2/2] btrfs: Use reada_control pointer instead of void pointer Goldwyn Rodrigues
2021-04-07 4:40 ` Anand Jain
2021-04-07 15:49 ` riteshh
2021-04-23 11:28 ` David Sterba
2021-04-06 23:59 ` Anand Jain [this message]
2021-04-07 15:53 ` [PATCH 1/2] btrfs: Remove unused function btrfs_reada_detach() riteshh
2021-04-23 11:19 ` David Sterba
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=2bce898b-bb2b-cedb-1b09-cecd48b5e73d@oracle.com \
--to=anand.jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rgoldwyn@suse.com \
--cc=rgoldwyn@suse.de \
/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).