From: David Sterba <dsterba@suse.com>
To: clm@fb.com
Cc: linux-btrfs@vger.kernel.org, David Sterba <dsterba@suse.com>
Subject: [PULL] Btrfs for 4.7, part 2
Date: Thu, 26 May 2016 11:27:06 +0200 [thread overview]
Message-ID: <cover.1464254502.git.dsterba@suse.com> (raw)
Hi,
please pull a few more patches that did not go to pull #1 for 4.7, minor
cleanups and fixes. Thanks.
The following changes since commit c315ef8d9db7f1a0ebd023a395ebdfde1c68057e:
Merge branch 'for-chris-4.7' of git://git.kernel.org/pub/scm/linux/kernel/git/fdmanana/linux into for-linus-4.7 (2016-05-17 14:43:19 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-chris
for you to fetch changes up to 4c6143dd497901e3537dc4324dc203dfda442009:
Merge branch 'dev/comp-workspaces' into for-chris-4.7-20160525 (2016-05-25 22:51:04 +0200)
----------------------------------------------------------------
David Sterba (17):
btrfs: rename and document compression workspace members
btrfs: preallocate compression workspaces
btrfs: make find_workspace always succeed
btrfs: make find_workspace warn if there are no workspaces
btrfs: sink gfp parameter to set_extent_bits
btrfs: sink gfp parameter to clear_extent_bits
btrfs: sink gfp parameter to clear_record_extent_bits
btrfs: sink gfp parameter to clear_extent_dirty
btrfs: sink gfp parameter to set_extent_delalloc
btrfs: sink gfp parameter to set_extent_defrag
btrfs: sink gfp parameter to set_extent_new
btrfs: sink gfp parameter to set_record_extent_bits
btrfs: untangle gotos a bit in __set_extent_bit
btrfs: untangle gotos a bit in __clear_extent_bit
btrfs: untangle gotos a bit in convert_extent_bit
btrfs: make state preallocation more speculative in __set_extent_bit
btrfs: sink gfp parameter to convert_extent_bit
Liu Bo (2):
Btrfs: free sys_array eb as soon as possible
Btrfs: fix unexpected return value of fiemap
Nicholas D Steeves (1):
btrfs: fix string and comment grammatical issues and typos
Zhao Lei (1):
btrfs: scrub: Set bbio to NULL before calling btrfs_map_block
next reply other threads:[~2016-05-26 9:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 9:27 David Sterba [this message]
2016-05-27 0:14 ` [PULL] Btrfs for 4.7, part 2 Chris Mason
2016-05-27 11:18 ` David Sterba
2016-05-27 14:35 ` Chris Mason
2016-05-27 15:42 ` Chris Mason
2016-05-28 5:14 ` Anand Jain
2016-05-29 12:21 ` Chris Mason
2016-06-14 10:52 ` Anand Jain
2016-06-14 10:55 ` [PATCH 1/2] btrfs: reorg btrfs_close_one_device() Anand Jain
2016-06-14 10:55 ` [PATCH 2/2] btrfs: wait for bdev put Anand Jain
2016-06-18 16:34 ` Holger Hoffstätte
2016-06-20 8:33 ` Anand Jain
2016-06-21 10:24 ` [PATCH v2 " Anand Jain
2016-06-21 11:46 ` Holger Hoffstätte
2016-06-21 13:00 ` Chris Mason
2016-06-22 10:18 ` Anand Jain
2016-06-22 21:47 ` Chris Mason
2016-06-23 13:07 ` Anand Jain
2016-06-23 12:54 ` [PATCH v3 2/2] btrfs: make sure device is synced before return Anand Jain
2016-06-23 14:27 ` Chris Mason
2016-07-08 14:13 ` 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=cover.1464254502.git.dsterba@suse.com \
--to=dsterba@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.