From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: dsterba@suse.cz
Subject: [PATCH 0/5] Cleanups for later btrfs_alloc_chunk() rework
Date: Wed, 3 Jan 2018 15:13:01 +0800 [thread overview]
Message-ID: <20180103071306.11500-1-wqu@suse.com> (raw)
Just small cleanups for incoming btrfs_alloc_chunk() rework, which is
designed to allow btrfs_alloc_chunk() to be able to alloc meta chunk,
even current meta chunks are already full.
The cleanups are quite small, most of them are just removing unnecessary
parameters, and make some function static.
Qu Wenruo (5):
btrfs-progs: Use bool parameter to determine if we're allocating data
extent
btrfs-progs: volumes: Make find_free_dev_extent_start static
btrfs-progs: volumes: Remove unnecessary trans parameter
btrfs-progs: volumes: Remove unnecessary parameters when allocating
device extent
btrfs-progs: Remove unnecessary parameter for btrfs_add_block_group
cmds-check.c | 4 ++--
convert/main.c | 4 +---
ctree.h | 7 +++----
extent-tree.c | 31 ++++++++++++++++---------------
mkfs/main.c | 14 ++++----------
volumes.c | 35 ++++++++++++++---------------------
6 files changed, 40 insertions(+), 55 deletions(-)
--
2.15.1
next reply other threads:[~2018-01-03 7:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 7:13 Qu Wenruo [this message]
2018-01-03 7:13 ` [PATCH 1/5] btrfs-progs: Use bool parameter to determine if we're allocating data extent Qu Wenruo
2018-01-03 7:13 ` [PATCH 2/5] btrfs-progs: volumes: Make find_free_dev_extent_start static Qu Wenruo
2018-01-03 7:13 ` [PATCH 3/5] btrfs-progs: volumes: Remove unnecessary trans parameter Qu Wenruo
2018-01-03 7:13 ` [PATCH 4/5] btrfs-progs: volumes: Remove unnecessary parameters when allocating device extent Qu Wenruo
2018-01-03 7:13 ` [PATCH 5/5] btrfs-progs: Remove unnecessary parameter for btrfs_add_block_group Qu Wenruo
2018-01-23 18:31 ` David Sterba
2018-01-03 9:17 ` [PATCH 0/5] Cleanups for later btrfs_alloc_chunk() rework Su Yue
2018-01-04 13:54 ` Nikolay Borisov
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=20180103071306.11500-1-wqu@suse.com \
--to=wqu@suse.com \
--cc=dsterba@suse.cz \
--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).