From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Chris Mason <clm@fb.com>, btrfs <linux-btrfs@vger.kernel.org>
Subject: [GIT PULL] Fujitsu pull part1: cleanup
Date: Fri, 21 Aug 2015 10:18:20 +0800 [thread overview]
Message-ID: <55D68A6C.3010107@cn.fujitsu.com> (raw)
Hi Chris,
Would you please consider merging the following fixes for your
integration-4.3 branch?
https://github.com/adam900710/linux.git for_chris_4.3_part1_cleanup
Most of them are harmless cleanups, like removing unused
parameters/judgment, or comment/variant name change.
We have already tested them for about 2 days, and it would be safe.
Based on 46cd28555ffaa40162290dba203daad0ff6f7abd.
And can be merged with pull from Filipe automatically without any conflict.
P.S:
Schedule for rest pull:
Part2: btrfs/070 fix.
The patchset is already updated sometime ago, but we are using more
test to make sure it won't cause any new bug.
PartN: qgroup reserve space leak fix. (maybe for 4.4)
This one will involve some huge change in btrfs qgroup reserve
mechanism.
The idea is to keep a per-inode map for which range of space is
already reserved, to avoid double reserve for same range but only
freed once case.
It's still under development, and it may not be able to meet
current merge windows.
So it's will be for 4.4.
PartN+1: Metadata and data qgroup support. (maybe for 4.4 with PartN)
Some old patches from Yang, but needs some updates for new qgroup
accounting/reserve mechanism.
Thanks,
Qu
Qu Wenruo (1):
btrfs: async_thread: Fix workqueue 'max_active' value when
initializing
Tsutomu Itoh (1):
Btrfs: cleanup: remove unnecessary check before btrfs_free_path is
called
Zhao Lei (6):
btrfs: Update out-of-date "skip parity stripe" comment
btrfs: Remove noused chunk_tree and chunk_objectid from
scrub_enumerate_chunks and scrub_chunk
btrfs: Cleanup for btrfs_calc_num_tolerated_disk_barrier_failures
btrfs: Add raid56 support for updating
num_tolerated_disk_barrier_failures in btrfs_balance
btrfs: Remove useless condition in start_log_trans
btrfs: Remove unused arguments in tree-log.c
fs/btrfs/async-thread.c | 57 ++++++++++++++++++++++---------------
fs/btrfs/async-thread.h | 2 +-
fs/btrfs/dev-replace.c | 3 +-
fs/btrfs/disk-io.c | 76
+++++++++++++++++++++++--------------------------
fs/btrfs/disk-io.h | 1 +
fs/btrfs/inode.c | 3 +-
fs/btrfs/scrub.c | 12 ++------
fs/btrfs/tree-defrag.c | 3 +-
fs/btrfs/tree-log.c | 68 ++++++++++++++++++-------------------------
fs/btrfs/volumes.c | 21 +++-----------
10 files changed, 110 insertions(+), 136 deletions(-)
next reply other threads:[~2015-08-21 2:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 2:18 Qu Wenruo [this message]
2015-08-21 19:01 ` [GIT PULL] Fujitsu pull part1: cleanup Stefan Behrens
2015-08-24 2:30 ` Anand Jain
2015-08-27 1:11 ` Qu Wenruo
2015-08-31 18:48 ` Chris Mason
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=55D68A6C.3010107@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=clm@fb.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).