public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Cc: aelder@sgi.com
Subject: [GIT PULL] xfs: fixes for 2.6.39
Date: Fri, 8 Apr 2011 15:11:37 +1000	[thread overview]
Message-ID: <20110408051137.GW31057@dastard> (raw)

Hi Alex,

The series of reviewed fixes for 2.6.39 can be found in the git tree
below. Please pull.

Cheers,

Dave.


The following changes since commit 89b3600ccfb01aed6873bc499442fc0bed00bbdd:

  xfs: fix unreferenced var error in xfs_buf.c (2011-03-30 23:34:20 -0500)

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 (9):
      xfs: fix extent format buffer allocation size
      xfs: introduce a xfssyncd workqueue
      xfs: convert ENOSPC inode flushing to use new syncd workqueue
      xfs: introduce background inode reclaim work
      xfs: convert the xfsaild threads to a workqueue
      xfs: clean up code layout in xfs_trans_ail.c
      xfs: push the AIL from memory reclaim and periodic sync
      xfs: catch bad block numbers freeing extents.
      xfs: convert log tail checking to a warning

 fs/xfs/linux-2.6/xfs_super.c |  129 +++++---------
 fs/xfs/linux-2.6/xfs_sync.c  |  228 ++++++++++++-----------
 fs/xfs/linux-2.6/xfs_sync.h  |    2 +
 fs/xfs/xfs_alloc.c           |   30 +++-
 fs/xfs/xfs_inode_item.c      |   67 ++++---
 fs/xfs/xfs_log.c             |   38 +++-
 fs/xfs/xfs_log_priv.h        |    1 +
 fs/xfs/xfs_mount.h           |    9 +-
 fs/xfs/xfs_trans_ail.c       |  421 +++++++++++++++++++++++-------------------
 fs/xfs/xfs_trans_priv.h      |   22 ++-
 10 files changed, 500 insertions(+), 447 deletions(-)
-- 
Dave Chinner
david@fromorbit.com

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

                 reply	other threads:[~2011-04-08  5:08 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=20110408051137.GW31057@dastard \
    --to=david@fromorbit.com \
    --cc=aelder@sgi.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