From: Alex Elder <aelder@sgi.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: My current xfs-for-2.6.38 tree....
Date: Tue, 04 Jan 2011 13:48:44 -0600 [thread overview]
Message-ID: <1294170524.2485.6.camel@doink> (raw)
In-Reply-To: <20110104064612.GK15179@dastard>
On Tue, 2011-01-04 at 17:46 +1100, Dave Chinner wrote:
> 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....
No that's OK, I'll take in everything that's reviewed
and ready to go and leave the rest for later. I've been
waiting for a pull request but this is fine with me.
-Alex
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-01-04 19:46 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
2011-01-04 19:48 ` Alex Elder [this message]
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=1294170524.2485.6.camel@doink \
--to=aelder@sgi.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox