From: David Sterba <dsterba@suse.com>
To: clm@fb.com
Cc: linux-btrfs@vger.kernel.org, David Sterba <dsterba@suse.com>
Subject: [PULL] Btrfs fixes for 4.9-rc4
Date: Tue, 1 Nov 2016 14:02:25 +0100 [thread overview]
Message-ID: <cover.1477327098.git.dsterba@suse.com> (raw)
Hi,
please pull the following assorted small fixes to 4.9, thanks. The branch is
"rc3" as it was meant for rc3 but I did not get to sending the pull request,
and I don't want to recreate the branch just because of a slightly wrong
name.
----------------------------------------------------------------
The following changes since commit d9ed71e5457c8c5bf1dc706e06468eab9e2aa87e:
Merge branch 'fst-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux into for-linus-4.9 (2016-10-12 13:16:00 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-4.9-rc3
for you to fetch changes up to 9d1032cc49a8a1065e79ee323de66bcb4fdbd535:
btrfs: fix WARNING in btrfs_select_ref_head() (2016-10-24 18:20:29 +0200)
----------------------------------------------------------------
Dan Carpenter (1):
Btrfs: remove some no-op casts
Goldwyn Rodrigues (1):
btrfs: qgroup: Prevent qgroup->reserved from going subzero
Liu Bo (1):
Btrfs: kill BUG_ON in do_relocation
Wang Xiaoguang (3):
btrfs: make file clone aware of fatal signals
btrfs: pass correct args to btrfs_async_run_delayed_refs()
btrfs: fix WARNING in btrfs_select_ref_head()
fs/btrfs/extent-tree.c | 3 +++
fs/btrfs/extent_io.c | 8 ++++----
fs/btrfs/inode.c | 13 +++++++++----
fs/btrfs/ioctl.c | 5 +++++
fs/btrfs/relocation.c | 9 ++++++++-
5 files changed, 29 insertions(+), 9 deletions(-)
next reply other threads:[~2016-11-01 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 13:02 David Sterba [this message]
2016-11-01 17:18 ` [PULL] Btrfs fixes for 4.9-rc4 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=cover.1477327098.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 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).