From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@lst.de>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 14/21] add get_maxrecs btree operation
Date: Wed, 30 Jul 2008 15:34:55 +1000 [thread overview]
Message-ID: <20080730053455.GO13395@disturbed> (raw)
In-Reply-To: <20080729193121.GO19104@lst.de>
On Tue, Jul 29, 2008 at 09:31:21PM +0200, Christoph Hellwig wrote:
> Factor xfs_btree_maxrecs into a per-btree operation.
>
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
->get_maxrecs was extracted out of my original patchset, right?
I didn't apply it to removing xfs_btree_maxrecs(), though. Good
idea. Looks fine to me.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2008-07-30 5:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 19:31 [PATCH 14/21] add get_maxrecs btree operation Christoph Hellwig
2008-07-30 5:34 ` Dave Chinner [this message]
2008-08-01 19:46 ` Christoph Hellwig
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=20080730053455.GO13395@disturbed \
--to=david@fromorbit.com \
--cc=hch@lst.de \
--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