From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH, needs a new owner] XFS multi-buftarg
Date: Fri, 20 Feb 2009 10:58:03 +1100 [thread overview]
Message-ID: <20090219235803.GF8830@disturbed> (raw)
In-Reply-To: <20090219192340.GA13964@infradead.org>
On Thu, Feb 19, 2009 at 02:23:40PM -0500, Christoph Hellwig wrote:
> On Thu, Feb 12, 2009 at 03:05:38PM +1100, Mark Goodwin wrote:
> >
> > Series of 10 patches, originally by Dave Chinner. This series
> > is unfinished, or needs forward porting to top-of-tree at the
> > very least. The feature implements some allocator/layout optimizations
> > by grouping AGs based on concat units, I think ;-)
> >
> > 02/10 xfs-factor-pag-freelist-check-2
>
> This one is an independent cleanup. It looks good to me and passes
> XFSQA. Dave, can you submit this one for 2.6.30?
Ok.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-02-20 0:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 4:05 [PATCH, needs a new owner] XFS multi-buftarg Mark Goodwin
2009-02-19 19:23 ` Christoph Hellwig
2009-02-19 23:58 ` Dave Chinner [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=20090219235803.GF8830@disturbed \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox