linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: David Sterba <dsterba@suse.cz>
Cc: Chris Mason <clm@fb.com>, linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: [GIT PULL] Btrfs device related fixes to support new features and bug fixes
Date: Sat, 10 Oct 2015 01:48:40 +0800	[thread overview]
Message-ID: <5617FDF8.3050909@oracle.com> (raw)


Hi David,

  Please consider the following fixes for your integration. These patches
  provide bug fixes, framework changes to support new features, and 3
  new features. They are mainly related to the device management like
  delete device by devid, introduce sysfs for device and pool, and fix
  the fs logging for multiple devices. All these patches has been sent
  to the mailing list as individual patches before.

      https://github.com/asj/btrfs-devel.git for-dave4

  (please note, the change log and subject line for some of the patches
  may contain minor updates).

  Anand Jain (16):
   btrfs: Pass the error code to the btrfs_std_error and log ret
   btrfs: Create a helper function to read the disk super
   btrfs: Maintain consistency in logging to help debugging
   btrfs: Device path change must be logged
   btrfs: Add missing brelse when superblock checksum fails
   btrfs: sysfs: Support seed devices in the sysfs layout
   btrfs: Create a framework to create pool attributes
   btrfs: Create helper function __check_raid_min_devices()
   btrfs: Clean up and optimize __check_raid_min_device()
   btrfs: Create helper btrfs_find_device_by_user_input()
   btrfs: Make use of btrfs_find_device_by_user_input()
   btrfs: Enhance btrfs_find_device_by_user_input() to check device path
   btrfs: Make use of btrfs_scratch_superblocks() in btrfs_rm_device()
   btrfs: Introduce device delete by devid
   btrfs: Introduce device pool sysfs attributes
   btrfs: Fix fs logging for multi device

  fs/btrfs/dev-replace.c     |  41 +--
  fs/btrfs/disk-io.c         |  23 +-
  fs/btrfs/ioctl.c           |  65 ++++-
  fs/btrfs/super.c           |   4 +-
  fs/btrfs/sysfs.c           | 624 
++++++++++++++++++++++++++++++++++++++++++++-
  fs/btrfs/sysfs.h           |  21 +-
  fs/btrfs/volumes.c         | 385 ++++++++++++++--------------
  fs/btrfs/volumes.h         |  16 +-
  include/uapi/linux/btrfs.h |  14 +-
  9 files changed, 937 insertions(+), 256 deletions(-)

                 reply	other threads:[~2015-10-09 17:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5617FDF8.3050909@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.cz \
    --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).