From: Nikolay Borisov <nborisov@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: Nikolay Borisov <nborisov@suse.com>
Subject: [PATCH 0/2] btrfstune fs_info cleanups
Date: Mon, 20 Aug 2018 16:28:03 +0300 [thread overview]
Message-ID: <1534771685-4924-1-git-send-email-nborisov@suse.com> (raw)
While inspecting btrfstune source code I came across 2 functions which needlessly
take fs_info argument. This small series rectifies this. No functional changes.
Nikolay Borisov (2):
btrfstune: Remove fs_info arg from change_device_uuid
btrfstune: Rename change_header_uuid to change_buffer_header_uuid
btrfstune.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
--
2.7.4
next 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 Nikolay Borisov [this message]
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
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-1-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).