public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: aelder@sgi.com
Cc: xfs@oss.sgi.com
Subject: Re: [GIT PULL] reviewed patches for -dev tree
Date: Wed, 14 Apr 2010 15:59:15 +1000	[thread overview]
Message-ID: <20100414055915.GI2493@dastard> (raw)
In-Reply-To: <20100413080357.GV2493@dastard>

On Tue, Apr 13, 2010 at 06:03:57PM +1000, Dave Chinner wrote:
> Alex,
> 
> Can you please pull from the tree indicated below. It contains all
> the outstanding reviewed patches not you committed to the xfs-dev
> tree.
> 
> Also, the following commits in the pull request need to be pushed to
> mainline for 2.6.34:
> 
> 	xfs: ensure that sync updates the log tail correctly
> 	xfs: don't warn on EAGAIN in inode reclaim
> 
> The first addresses a regression introduced in 2.6.34-rc1, the
> second silences a needless warning that is being reported on
> 2.6.33.

I just updated the branch with this commit appended:

	xfs: make the log ticket transaction id random

So it now looks like:

The following changes since commit 68a2ac777cca40ccc993512bcf457999be71cc36:
  Christoph Hellwig (1):
        xfs: clean up xlog_write_adv_cnt

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/dgc/xfs.git ..BRANCH.NOT.VERIFIED..

Alex Elder (6):
      xfs: add const qualifiers to xfs error function args
      xfs: fix min bufsize bugs in two places
      xfs: simplify XLOG_SECTOR_ROUND*()
      xfs: kill XLOG_SECTOR_ROUND*()
      xfs: encapsulate bbcount validity checking
      xfs: nothing special about 1-block log sector

Christoph Hellwig (1):
      xfs: remove xfs_dqmarker

Dave Chinner (8):
      xfs: ensure that sync updates the log tail correctly
      xfs: don't warn on EAGAIN in inode reclaim
      xfs: add log item recovery tracing
      xfs: convert the per-mount dquot list to use list heads
      xfs: remove duplicate code from dquot reclaim
      xfs: convert the dquot hash list to use list heads
      xfs: convert the dquot free list to use list heads
      xfs: make the log ticket transaction id random

 fs/xfs/linux-2.6/xfs_sync.c    |    4 +-
 fs/xfs/linux-2.6/xfs_trace.c   |    3 +
 fs/xfs/linux-2.6/xfs_trace.h   |  141 +++++++++++-
 fs/xfs/quota/xfs_dquot.c       |  120 ++++------
 fs/xfs/quota/xfs_dquot.h       |   35 +---
 fs/xfs/quota/xfs_qm.c          |  515 ++++++++++++++--------------------------
 fs/xfs/quota/xfs_qm.h          |   23 +--
 fs/xfs/quota/xfs_qm_stats.c    |    2 +-
 fs/xfs/quota/xfs_qm_syscalls.c |   38 ++--
 fs/xfs/quota/xfs_quota_priv.h  |   75 ------
 fs/xfs/xfs_buf_item.h          |    2 +-
 fs/xfs/xfs_error.c             |   30 ++--
 fs/xfs/xfs_error.h             |    9 +-
 fs/xfs/xfs_log.c               |   40 ++-
 fs/xfs/xfs_log_recover.c       |  155 +++++++++----
 fs/xfs/xfs_trans.h             |    9 +
 16 files changed, 563 insertions(+), 638 deletions(-)

-- 
Dave Chinner
david@fromorbit.com

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

  reply	other threads:[~2010-04-14  5:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-13  8:03 [GIT PULL] reviewed patches for -dev tree Dave Chinner
2010-04-14  5:59 ` Dave Chinner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-04-20  7:28 Dave Chinner

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=20100414055915.GI2493@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