public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@lst.de>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 6/6] move XFS_BMAP_SANITY_CHECK out of line
Date: Tue, 16 Sep 2008 16:31:46 +1000	[thread overview]
Message-ID: <20080916063146.GZ5811@disturbed> (raw)
In-Reply-To: <20080915004703.GG12213@lst.de>

On Mon, Sep 15, 2008 at 02:47:03AM +0200, Christoph Hellwig wrote:
> Move the XFS_BMAP_SANITY_CHECK macro out of line and make it a properly typed
> function.  Also pass the xfs_buf for the btree block instead of just the btree
> block header, as we will need some additional information for it to implement
> CRC checking of btree blocks.

Looks good.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2008-09-16  6:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-15  0:47 [PATCH 6/6] move XFS_BMAP_SANITY_CHECK out of line Christoph Hellwig
2008-09-16  6:31 ` Dave Chinner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-09-22 11:06 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=20080916063146.GZ5811@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