public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [GIT PULL] xfs: more fixes for 2.6.39
Date: Sat, 26 Mar 2011 09:37:18 +1100	[thread overview]
Message-ID: <20110325223718.GP26611@dastard> (raw)


Hi Alex,

Here is the latest round of commits for 2.6.39 rady for you to pull.
It's based on the current xfs-oss master branch.

Cheers,

Dave.


The following changes since commit 0c9ba97318fc9a905bcc1419b6966de061203a70:

  xfs: don't name variables "panic" (2011-03-11 16:34:51 -0600)

are available in the git repository at:
  git://git.kernel.org/pub/scm/linux/kernel/git/dgc/xfsdev.git xfs-for-2.6.39

Dave Chinner (6):
      xfs: preallocation transactions do not need to be synchronous
      vmap: flush vmap aliases when mapping fails
      xfs: introduce inode cluster buffer trylocks for xfs_iflush
      xfs: xfs_trans_read_buf() should return an error on failure
      xfs: register the inode cache shrinker before quotachecks
      xfs: stop using the page cache to back the buffer cache

 fs/xfs/linux-2.6/xfs_buf.c   |  355 +++++++++++-------------------------------
 fs/xfs/linux-2.6/xfs_buf.h   |   40 +-----
 fs/xfs/linux-2.6/xfs_file.c  |    6 +-
 fs/xfs/linux-2.6/xfs_ioctl.c |    4 +
 fs/xfs/linux-2.6/xfs_super.c |   36 +++--
 fs/xfs/linux-2.6/xfs_sync.c  |   30 ++++-
 fs/xfs/xfs_inode.c           |    2 +-
 fs/xfs/xfs_inode_item.c      |    6 +-
 fs/xfs/xfs_trans_buf.c       |    3 +-
 fs/xfs/xfs_vnodeops.c        |    3 +-
 fs/xfs/xfs_vnodeops.h        |    1 +
 11 files changed, 165 insertions(+), 321 deletions(-)
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

                 reply	other threads:[~2011-03-25 22:34 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=20110325223718.GP26611@dastard \
    --to=david@fromorbit.com \
    --cc=xfs@oss.sgi.com \
    /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