From: Nikolay Borisov <nborisov@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: Nikolay Borisov <nborisov@suse.com>
Subject: [PATCH 1/2] btrfstune: Remove fs_info arg from change_device_uuid
Date: Mon, 20 Aug 2018 16:28:04 +0300 [thread overview]
Message-ID: <1534771685-4924-2-git-send-email-nborisov@suse.com> (raw)
In-Reply-To: <1534771685-4924-1-git-send-email-nborisov@suse.com>
This function already takes an extent buffer that contains a reference
to the fs_info. Use that and reduce argument count. No functional
changes.
Signed-off-by: Nikolay Borisov <nborisov@suse.com>
---
btrfstune.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/btrfstune.c b/btrfstune.c
index 889b931c55d8..723317a00f3a 100644
--- a/btrfstune.c
+++ b/btrfstune.c
@@ -179,10 +179,10 @@ static int change_extents_uuid(struct btrfs_fs_info *fs_info)
return ret;
}
-static int change_device_uuid(struct btrfs_fs_info *fs_info, struct extent_buffer *eb,
- int slot)
+static int change_device_uuid(struct extent_buffer *eb, int slot)
{
struct btrfs_dev_item *di;
+ struct btrfs_fs_info *fs_info = eb->fs_info;
int ret = 0;
di = btrfs_item_ptr(eb, slot, struct btrfs_dev_item);
@@ -217,7 +217,7 @@ static int change_devices_uuid(struct btrfs_fs_info *fs_info)
if (key.type != BTRFS_DEV_ITEM_KEY ||
key.objectid != BTRFS_DEV_ITEMS_OBJECTID)
goto next;
- ret = change_device_uuid(fs_info, path.nodes[0], path.slots[0]);
+ ret = change_device_uuid(path.nodes[0], path.slots[0]);
if (ret < 0)
goto out;
next:
--
2.7.4
next prev parent reply other threads:[~2018-08-20 16:43 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 ` Nikolay Borisov [this message]
2018-08-20 13:31 ` [PATCH 1/2] btrfstune: Remove fs_info arg from change_device_uuid 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
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=1534771685-4924-2-git-send-email-nborisov@suse.com \
--to=nborisov@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).