All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <josef@redhat.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: [GIT PULL] Btrfs updates for 3.1
Date: Fri, 01 Jul 2011 16:39:45 -0400	[thread overview]
Message-ID: <4E0E3091.9060704@redhat.com> (raw)

Hey Chris,

Since I'm going on vacation next week I wanted to get everything ready for you
in case you get bored with fsck and want to put together a 3.1 tree :).  If you
can pull

git://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-work.git for-chris

It is based on your for-linus branch.  Here is the shortlog and diffstat

Josef Bacik (7):
      Btrfs: try to only do one btrfs_search_slot in do_setxattr
      Btrfs: do transaction space reservation before joining the transaction
      Btrfs: serialize flushers in reserve_metadata_bytes
      Btrfs: use the normal checksumming infrastructure for free space cache
      Btrfs: fix how we merge extent states and deal with cached states
      Btrfs: use a worker thread to do caching
      Btrfs: don't panic if we get an error while balancing

 fs/btrfs/ctree.h            |   10 ++-
 fs/btrfs/dir-item.c         |    9 +--
 fs/btrfs/disk-io.c          |    6 ++
 fs/btrfs/extent-tree.c      |  136 +++++++++++++++++------------------
 fs/btrfs/extent_io.c        |   23 +++---
 fs/btrfs/free-space-cache.c |  169 +++++++++++++++----------------------------
 fs/btrfs/transaction.c      |   36 +++++-----
 fs/btrfs/volumes.c          |    3 +-
 fs/btrfs/xattr.c            |   54 +++++++-------
 9 files changed, 196 insertions(+), 250 deletions(-)

Thanks,

Josef

             reply	other threads:[~2011-07-01 20:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-01 20:39 Josef Bacik [this message]
2011-07-02 21:25 ` [GIT PULL] Btrfs updates for 3.1 Josef Bacik
2011-07-11  0:20   ` Mitch Harder
2011-07-11 13:33     ` Josef Bacik

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=4E0E3091.9060704@redhat.com \
    --to=josef@redhat.com \
    --cc=chris.mason@oracle.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.