From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/2] btrfstune: Rename change_header_uuid to change_buffer_header_uuid
Date: Mon, 20 Aug 2018 21:34:37 +0800 [thread overview]
Message-ID: <55ec64a2-d2ec-d12f-387d-98b40eb78884@gmx.com> (raw)
In-Reply-To: <1534771685-4924-3-git-send-email-nborisov@suse.com>
On 2018/8/20 下午9:28, Nikolay Borisov wrote:
> Rename the function so its name falls in line with the rest of btrfs
> nomenclature. So when we change the uuid of the header it's in fact
> of the buffer header.
We have setget functions like btrfs_header_nritems() or
btrfs_header_bytenr(), IMHO both ways make sense.
Although I have no objection against current modification.
> Also remove the root argument since it's used
> solely to take a reference to fs_info which can be done via the
> mandatory eb argument. No functional changes.>
> Signed-off-by: Nikolay Borisov <nborisov@suse.com>
Reviewed-by: Qu Wenruo <wqu@suse.com>
Thanks,
Qu
> ---
> btrfstune.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/btrfstune.c b/btrfstune.c
> index 723317a00f3a..3745a00c46ae 100644
> --- a/btrfstune.c
> +++ b/btrfstune.c
> @@ -91,9 +91,9 @@ static int set_super_incompat_flags(struct btrfs_root *root, u64 flags)
> return ret;
> }
>
> -static int change_header_uuid(struct btrfs_root *root, struct extent_buffer *eb)
> +static int change_buffer_header_uuid(struct extent_buffer *eb)
> {
> - struct btrfs_fs_info *fs_info = root->fs_info;
> + struct btrfs_fs_info *fs_info = eb->fs_info;
> int same_fsid = 1;
> int same_chunk_tree_uuid = 1;
> int ret;
> @@ -157,7 +157,7 @@ static int change_extents_uuid(struct btrfs_fs_info *fs_info)
> ret = PTR_ERR(eb);
> goto out;
> }
> - ret = change_header_uuid(root, eb);
> + ret = change_buffer_header_uuid(eb);
> free_extent_buffer(eb);
> if (ret < 0) {
> error("failed to change uuid of tree block: %llu",
>
next prev parent reply other threads:[~2018-08-20 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 13:28 [PATCH 0/2] btrfstune fs_info cleanups Nikolay Borisov
2018-08-20 13:28 ` [PATCH 1/2] btrfstune: Remove fs_info arg from change_device_uuid Nikolay Borisov
2018-08-20 13:31 ` Qu Wenruo
2018-08-20 13:28 ` [PATCH 2/2] btrfstune: Rename change_header_uuid to change_buffer_header_uuid Nikolay Borisov
2018-08-20 13:34 ` Qu Wenruo [this message]
2018-08-20 13:44 ` Nikolay Borisov
2018-10-25 16:38 ` [PATCH 0/2] btrfstune fs_info cleanups 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=55ec64a2-d2ec-d12f-387d-98b40eb78884@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@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;
as well as URLs for NNTP newsgroup(s).