From: Nikolay Borisov <nborisov@suse.com>
To: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: remove the unused btrfs_fs_info::seeding member
Date: Fri, 15 Apr 2022 10:58:23 +0300 [thread overview]
Message-ID: <8f8e1a81-47e7-1ca4-0bf2-043716cd5dd1@suse.com> (raw)
In-Reply-To: <0965ac68fbcb31b5cc4b70da84725e887fde847c.1650007153.git.wqu@suse.com>
On 15.04.22 г. 10:19 ч., Qu Wenruo wrote:
> This member is not used by anyone, just remove it.
>
> Signed-off-by: Qu Wenruo <wqu@suse.com>
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
> ---
> kernel-shared/volumes.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/kernel-shared/volumes.h b/kernel-shared/volumes.h
> index 5cfe7e39f6b8..f9ca0a86e319 100644
> --- a/kernel-shared/volumes.h
> +++ b/kernel-shared/volumes.h
> @@ -94,7 +94,6 @@ struct btrfs_fs_devices {
> struct list_head devices;
> struct list_head list;
>
> - int seeding;
> struct btrfs_fs_devices *seed;
>
> enum btrfs_chunk_allocation_policy chunk_alloc_policy;
next prev parent reply other threads:[~2022-04-15 7:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 7:19 [PATCH] btrfs-progs: remove the unused btrfs_fs_info::seeding member Qu Wenruo
2022-04-15 7:58 ` Nikolay Borisov [this message]
2022-04-29 20:13 ` 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=8f8e1a81-47e7-1ca4-0bf2-043716cd5dd1@suse.com \
--to=nborisov@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.com \
/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