From: Nikolay Borisov <nborisov@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: Nikolay Borisov <nborisov@suse.com>
Subject: [PATCH 00/11] Summer argument cleanup
Date: Mon, 28 May 2018 09:36:39 +0300 [thread overview]
Message-ID: <1527489410-3564-1-git-send-email-nborisov@suse.com> (raw)
Hello,
Here is yet another series removing a bunch of extraneous argument. The series
constitutes no functional changes. Some of the function actually have a kernel
counterpart (btrfs_lookup_extent_info/clean_tree_block). However the former's
userspace signature differs and the patch in this series makes it identical to
the kernel one.
Nikolay Borisov (11):
btrfs-progs: check: Remove root argument from delete_extent_records
btrfs-progs: check: Remove root parameter from
btrfs_fix_block_accounting
btrfs-progs: check: Remove root parameter from del_pending_extents
btrfs-progs: check: Remove root argument from finish_current_insert
btrfs-progs: check: Make update_pinned_extents take btrfs_fs_info
btrfs-progs: Remove unused argument from clean_tree_block
btrfs-progs: check: Remove unused root argument from
btrfs_extent_post_op
btrfs-progs: Change btrfs_root to btrfs_fs_info argument in
btrfs_lookup_extent_info
btrfs-progs: Remove root argument from btrfs_set_block_flags
btrfs-progs: Remove root argument from write_one_cache_group
btrfs-progs: Remove fs_info argument from write_ctree_super
check/main.c | 31 +++++++-------
check/mode-lowmem.c | 6 +--
ctree.c | 17 ++++----
ctree.h | 13 +++---
disk-io.c | 9 ++--
disk-io.h | 6 +--
extent-tree.c | 121 ++++++++++++++++++++++++----------------------------
free-space-tree.c | 2 +-
transaction.c | 2 +-
9 files changed, 96 insertions(+), 111 deletions(-)
--
2.7.4
next reply other threads:[~2018-05-28 16:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 6:36 Nikolay Borisov [this message]
2018-05-28 6:36 ` [PATCH 01/11] btrfs-progs: check: Remove root argument from delete_extent_records Nikolay Borisov
2018-05-28 6:36 ` [PATCH 02/11] btrfs-progs: check: Remove root parameter from btrfs_fix_block_accounting Nikolay Borisov
2018-05-28 6:36 ` [PATCH 03/11] btrfs-progs: check: Remove root parameter from del_pending_extents Nikolay Borisov
2018-05-28 6:36 ` [PATCH 04/11] btrfs-progs: check: Remove root argument from finish_current_insert Nikolay Borisov
2018-05-28 6:36 ` [PATCH 05/11] btrfs-progs: check: Make update_pinned_extents take btrfs_fs_info Nikolay Borisov
2018-05-28 6:36 ` [PATCH 06/11] btrfs-progs: Remove unused argument from clean_tree_block Nikolay Borisov
2018-05-28 6:36 ` [PATCH 07/11] btrfs-progs: check: Remove unused root argument from btrfs_extent_post_op Nikolay Borisov
2018-05-28 6:36 ` [PATCH 08/11] btrfs-progs: Change btrfs_root to btrfs_fs_info argument in btrfs_lookup_extent_info Nikolay Borisov
2018-05-28 6:36 ` [PATCH 09/11] btrfs-progs: Remove root argument from btrfs_set_block_flags Nikolay Borisov
2018-05-28 6:36 ` [PATCH 10/11] btrfs-progs: Remove root argument from write_one_cache_group Nikolay Borisov
2018-05-28 6:36 ` [PATCH 11/11] btrfs-progs: Remove fs_info argument from write_ctree_super Nikolay Borisov
2018-05-29 1:06 ` [PATCH 00/11] Summer argument cleanup Lu Fengqi
2018-05-31 11:34 ` 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=1527489410-3564-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).