linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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-rc5
Date: Thu, 10 Nov 2016 16:00:57 +0100	[thread overview]
Message-ID: <cover.1478789584.git.dsterba@suse.com> (raw)

Hi,

two minor error handling fixes and one fix for balance sttus item that goes
back to 4.4.

The branch continues from my last pull that went to Linus' tree, so it would
be a good idea to do the same as before. I've added a signed tag for branch.

----------------------------------------------------------------
The following changes since commit 9d1032cc49a8a1065e79ee323de66bcb4fdbd535:

  btrfs: fix WARNING in btrfs_select_ref_head() (2016-10-24 18:20:29 +0200)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-4.9-rc5

for you to fetch changes up to 3ed73b672c8707cab47ef0caf5d0c2a377ad70f2:

  btrfs: Call kunmap if zlib_inflateInit2 fails (2016-11-07 18:07:03 +0100)

----------------------------------------------------------------
Christophe JAILLET (1):
      btrfs: remove redundant check of btrfs_iget return value

David Sterba (1):
      btrfs: store and load values of stripes_min/stripes_max in balance status item

Nick Terrell (1):
      btrfs: Call kunmap if zlib_inflateInit2 fails

 fs/btrfs/ctree.h            | 4 ++++
 fs/btrfs/free-space-cache.c | 2 --
 fs/btrfs/zlib.c             | 1 +
 3 files changed, 5 insertions(+), 2 deletions(-)

             reply	other threads:[~2016-11-10 15:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-10 15:00 David Sterba [this message]
2016-11-11 20:45 ` [PULL] Btrfs fixes for 4.9-rc5 Chris Mason
2016-11-14 12:46   ` 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.1478789584.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).