linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: clm@fb.com
Cc: David Sterba <dsterba@suse.com>, linux-btrfs@vger.kernel.org
Subject: [PULL] Btrfs updates for 4.11-rc2
Date: Thu,  9 Mar 2017 14:55:00 +0100	[thread overview]
Message-ID: <cover.1489067273.git.dsterba@suse.com> (raw)

Hi,

there's a regression fix for the assertion failure reported by Dave Jones, the
rest of patches are minor updates. Please pull, thanks.

The following changes since commit e9f467d028cd7d8bee2a4d6c4fb806caf8cd580b:

  Merge branch 'for-chris-4.11-part2' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux into for-linus-4.11 (2017-02-28 14:35:09 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-chris-4.11-rc2

for you to fetch changes up to 94b5a2924fc0ec2bb2347ca31156be8fabe907c4:

  Btrfs: consistent usage of types in balance_args (2017-03-09 14:23:00 +0100)

----------------------------------------------------------------
Dmitry V. Levin (2):
      btrfs: remove btrfs_err_str function from uapi/linux/btrfs.h
      MAINTAINERS: add btrfs file entries for include directories

Goldwyn Rodrigues (1):
      btrfs: No need to check !(flags & MS_RDONLY) twice

Hans van Kranenburg (1):
      Btrfs: consistent usage of types in balance_args

Liu Bo (2):
      Btrfs: update comments in cache_save_setup
      Btrfs: fix regression in lock_delalloc_pages

 MAINTAINERS                |  2 ++
 fs/btrfs/extent-tree.c     |  3 ++-
 fs/btrfs/extent_io.c       |  3 ++-
 fs/btrfs/super.c           |  3 +--
 include/uapi/linux/btrfs.h | 37 +++++--------------------------------
 5 files changed, 12 insertions(+), 36 deletions(-)

             reply	other threads:[~2017-03-09 13:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-09 13:55 David Sterba [this message]
2017-03-17 20:56 ` [PULL] Btrfs updates for 4.11-rc2 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.1489067273.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).