From: Gu Jinxiang <gujx@cn.fujitsu.com>
To: <linux-btrfs@vger.kernel.org>
Cc: <quwenruo.btrfs@gmx.com>
Subject: [PATCH v2 0/7] btrfs-progs: Do some clean up to be consistent
Date: Fri, 26 Jan 2018 15:25:59 +0800 [thread overview]
Message-ID: <1516951566-21777-1-git-send-email-gujx@cn.fujitsu.com> (raw)
Patch 1~4 and 7: clean up use of btrfs_root.
Patch 5: remove redundancy value assignment.
Patch 6: remove no longer be used function define.
Changelog:
v2->v1:
Patch 2,4: To be consistent with kernel, change macro to inline function.
Patch 3:
Change macro to inline function to be consistent with kernel.
And change the function body to match kernel.
Gu Jinxiang (7):
btrfs-progs: Use fs_info instead of root for BTRFS_LEAF_DATA_SIZE
btrfs-progs: Use fs_info instead of root for BTRFS_NODEPTRS_PER_BLOCK
btrfs-progs: Use fs_info instead of root for
BTRFS_MAX_INLINE_DATA_SIZE
btrfs-progs: Use fs_info instead of root for BTRFS_MAX_XATTR_SIZE
btrfs-progs: do clean up for redundancy value assignment
btrfs-progs: remove no longer be used btrfs_alloc_extent
btrfs-progs: Cleanup use of root in leaf_data_end
cmds-check.c | 10 ++---
convert/source-ext2.c | 4 +-
convert/source-reiserfs.c | 6 +--
ctree.c | 96 +++++++++++++++++++++++++----------------------
ctree.h | 45 +++++++++++++---------
dir-item.c | 3 +-
extent-tree.c | 1 -
file-item.c | 2 +-
mkfs/main.c | 4 +-
print-tree.c | 2 +-
quick-test.c | 2 +-
volumes.c | 2 +-
12 files changed, 97 insertions(+), 80 deletions(-)
--
2.14.3
next reply other threads:[~2018-01-26 7:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 7:25 Gu Jinxiang [this message]
2018-01-26 7:26 ` [PATCH v2 1/7] btrfs-progs: Use fs_info instead of root for BTRFS_LEAF_DATA_SIZE Gu Jinxiang
2018-01-26 7:26 ` [PATCH v2 2/7] btrfs-progs: Use fs_info instead of root for BTRFS_NODEPTRS_PER_BLOCK Gu Jinxiang
2018-01-26 7:26 ` [PATCH v2 3/7] btrfs-progs: Use fs_info instead of root for BTRFS_MAX_INLINE_DATA_SIZE Gu Jinxiang
2018-01-26 7:26 ` [PATCH v2 4/7] btrfs-progs: Use fs_info instead of root for BTRFS_MAX_XATTR_SIZE Gu Jinxiang
2018-01-26 7:26 ` [PATCH v2 5/7] btrfs-progs: do clean up for redundancy value assignment Gu Jinxiang
2018-01-26 7:26 ` [PATCH v2 6/7] btrfs-progs: remove no longer be used btrfs_alloc_extent Gu Jinxiang
2018-01-26 7:26 ` [PATCH v2 7/7] btrfs-progs: Cleanup use of root in leaf_data_end Gu Jinxiang
2018-01-30 7:36 ` Qu Wenruo
2018-01-31 16:12 ` David Sterba
2018-01-26 8:18 ` [PATCH v2 0/7] btrfs-progs: Do some clean up to be consistent Qu Wenruo
2018-01-31 16:14 ` 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=1516951566-21777-1-git-send-email-gujx@cn.fujitsu.com \
--to=gujx@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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).