From: Christoph Hellwig <hch@lst.de>
To: xfs@oss.sgi.com
Subject: [PATCH 0/6] btree cleanups V2
Date: Mon, 22 Sep 2008 13:06:23 +0200 [thread overview]
Message-ID: <20080922110623.GA26007@lst.de> (raw)
Here's a set of a few small btree cleanup patches. Most of them are in
preparation of adding CRC support to the btree blocks. All these
require the generic btree patchset to be applied first.
Compared to version 1 I've addressed Dave's review comments. I decided to
keep XFS_BMAP_BROOT_PTR_ADDR because it's used a few times and already in
long enough lines that would start to get unreadable if we expanded it. I've
also left the odd boolean arguments to the maxrecs functions as is for now,
but I have some plans to tackle that from a higher level view later.
--
reply other threads:[~2008-09-22 11:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080922110623.GA26007@lst.de \
--to=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