From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: My current xfs-for-2.6.38 tree....
Date: Tue, 4 Jan 2011 17:46:12 +1100 [thread overview]
Message-ID: <20110104064612.GK15179@dastard> (raw)
In-Reply-To: <20110104055441.GA9870@infradead.org>
On Tue, Jan 04, 2011 at 12:54:41AM -0500, Christoph Hellwig wrote:
> On Tue, Jan 04, 2011 at 04:02:59PM +1100, Dave Chinner wrote:
> > Folks,
> >
> > FYI, my current xfs-for-2.6.38 tree has just been updated. Changes
> > since last update:
> >
> > - dropped the per-cpu superblock counter cleanup patches
> > from it so we can get it right before merging.
> > - added unaligned aio/dio write fix series (needs review)
> > - added log covering idle fix (needs review)
> > - added superblock write error hang fix (needs review)
> >
> > The tree can be found here (when the rsync updates git.kernel.org):
>
> I'll try to get to review the new patches, but can we please get the
> metadata scalability patches into the xfs tree and thus linux-next ASAP?
> The merge window is about to open, and we really need to get that stuff
> in now.
That's all first in the branch and reviewed, so Alex should be able
to simply merge up to the last commit in that part of the series from
the branch I posted.
Alex, if you want I can set up a separate branch for the metadata
scalability series....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-01-04 6:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 5:02 My current xfs-for-2.6.38 tree Dave Chinner
2011-01-04 5:54 ` Christoph Hellwig
2011-01-04 6:46 ` Dave Chinner [this message]
2011-01-04 19:48 ` Alex Elder
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=20110104064612.GK15179@dastard \
--to=david@fromorbit.com \
--cc=hch@infradead.org \
--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 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.