From: Liu Bo <bo.li.liu@oracle.com>
To: David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: remove unused ulist members
Date: Fri, 10 Feb 2017 07:19:06 -0800 [thread overview]
Message-ID: <20170210151906.GA30334@localhost.localdomain> (raw)
In-Reply-To: <20170209154743.11186-1-dsterba@suse.com>
On Thu, Feb 09, 2017 at 04:47:43PM +0100, David Sterba wrote:
> Commit "btrfs: ulist: Add ulist_del() function" (d4b804045924d7f8)
> removed some debugging code but left the structure defintions.
>
Reviewed-by: Liu Bo <bo.li.liu@oracle.com>
> Signed-off-by: David Sterba <dsterba@suse.com>
> ---
> fs/btrfs/ulist.h | 7 -------
> 1 file changed, 7 deletions(-)
>
> diff --git a/fs/btrfs/ulist.h b/fs/btrfs/ulist.h
> index a01a2c45825f..007b22fff3f9 100644
> --- a/fs/btrfs/ulist.h
> +++ b/fs/btrfs/ulist.h
> @@ -19,9 +19,6 @@
> *
> */
> struct ulist_iterator {
> -#ifdef CONFIG_BTRFS_DEBUG
> - int i;
> -#endif
> struct list_head *cur_list; /* hint to start search */
> };
>
> @@ -32,10 +29,6 @@ struct ulist_node {
> u64 val; /* value to store */
> u64 aux; /* auxiliary value saved along with the val */
>
> -#ifdef CONFIG_BTRFS_DEBUG
> - int seqnum; /* sequence number this node is added */
> -#endif
> -
> struct list_head list; /* used to link node */
> struct rb_node rb_node; /* used to speed up search */
> };
> --
> 2.10.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-02-10 18:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 15:47 [PATCH] btrfs: remove unused ulist members David Sterba
2017-02-10 0:56 ` Qu Wenruo
2017-02-10 15:19 ` Liu Bo [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=20170210151906.GA30334@localhost.localdomain \
--to=bo.li.liu@oracle.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).