From: Chris Mason <chris.mason@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Btrfs pull request
Date: Sun, 6 Nov 2011 19:35:14 -0500 [thread overview]
Message-ID: <20111107003514.GB4339@shiny> (raw)
In-Reply-To: <20111106183851.GA4339@shiny>
On Sun, Nov 06, 2011 at 01:38:51PM -0500, Chris Mason wrote:
> Hi everyone,
>
> This pull request is pretty beefy, it ended up merging a number of long
> running projects and cleanup queues. I've got btrfs patches in the new
> kernel.org btrfs repo. There are two different branches with the same
> changes. for-linus is against 3.1 and has also been tested against
> Linus' tree as of yesterday.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
Well, I had one more commit in my working directory that I neglected to
run git commit on. It fixes an oops during log replay.
The new head of my for-linus branch is:
commit 7c7e82a77fe3d89ae50824aa7c897454675eb4c4
Author: Chris Mason <chris.mason@oracle.com>
Date: Sun Nov 6 18:50:56 2011 -0500
Btrfs: check for a null fs root when writing to the backup root log
If you're pulling just that one commit it'll have this diffstat:
disk-io.c | 13 ++++++++++---
1 file changed, 10 insertions(+), 3 deletions(-)
The diffstat for the whole bunch is below. Sorry for the noise.
-chris
Total: (114) commits
fs/btrfs/Makefile | 3 +-
fs/btrfs/acl.c | 17 +-
fs/btrfs/backref.c | 776 +++++++++++++++++++++++++++++++++++
fs/btrfs/backref.h | 62 +++
fs/btrfs/btrfs_inode.h | 17 +-
fs/btrfs/compression.c | 3 +-
fs/btrfs/ctree.c | 10 +-
fs/btrfs/ctree.h | 198 ++++++++--
fs/btrfs/delayed-inode.c | 50 ++-
fs/btrfs/disk-io.c | 441 +++++++++++++++++---
fs/btrfs/disk-io.h | 4 +-
fs/btrfs/extent-tree.c | 848 +++++++++++++++++++++++---------------
fs/btrfs/extent_io.c | 614 +++++++++++++++++++++++++++-
fs/btrfs/extent_io.h | 23 +-
fs/btrfs/file-item.c | 17 +-
fs/btrfs/file.c | 25 +-
fs/btrfs/free-space-cache.c | 926 +++++++++++++++++++++++++----------------
fs/btrfs/inode-map.c | 6 +-
fs/btrfs/inode.c | 457 +++++++--------------
fs/btrfs/ioctl.c | 227 +++++++++--
fs/btrfs/ioctl.h | 29 ++
fs/btrfs/print-tree.c | 8 +-
fs/btrfs/reada.c | 951 +++++++++++++++++++++++++++++++++++++++++++
fs/btrfs/relocation.c | 24 +-
fs/btrfs/scrub.c | 591 ++++++++++++++++++++++-----
fs/btrfs/super.c | 298 +++++++++-----
fs/btrfs/transaction.c | 146 +++----
fs/btrfs/tree-log.c | 19 +-
fs/btrfs/volumes.c | 207 ++++++----
fs/btrfs/volumes.h | 18 +-
fs/btrfs/xattr.c | 11 +
31 files changed, 5423 insertions(+), 1603 deletions(-)
next prev parent reply other threads:[~2011-11-07 0:35 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 18:38 [GIT PULL] Btrfs pull request Chris Mason
2011-11-06 19:29 ` Andrea Gelmini
2011-11-06 19:29 ` Andrea Gelmini
2011-11-07 9:37 ` Arne Jansen
2011-11-07 9:49 ` Roman Mamedov
2011-11-07 9:57 ` Arne Jansen
2011-11-07 12:49 ` Andrea Gelmini
2011-11-07 12:42 ` Andrea Gelmini
2011-11-07 12:45 ` Arne Jansen
2011-11-07 12:50 ` Andrea Gelmini
2011-11-08 7:47 ` Arne Jansen
2011-11-09 1:07 ` Chris Mason
2011-11-09 7:48 ` Christoph Hellwig
2011-11-09 9:06 ` Arne Jansen
2011-11-09 10:11 ` Christoph Hellwig
2011-11-09 12:11 ` Chris Mason
2011-11-09 10:29 ` Jan Schmidt
2011-11-09 10:34 ` Christoph Hellwig
2011-11-09 10:49 ` Jan Schmidt
2011-11-09 12:12 ` Chris Mason
2011-11-07 0:35 ` Chris Mason [this message]
2011-11-08 17:55 ` Dan Merillat
2011-11-08 17:55 ` Dan Merillat
2011-11-08 18:27 ` Chris Mason
2011-11-08 18:27 ` Chris Mason
2011-11-08 20:17 ` Chris Mason
2011-11-08 20:17 ` Chris Mason
2011-11-09 6:53 ` Dan Merillat
2011-11-09 6:53 ` Dan Merillat
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=20111107003514.GB4339@shiny \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.