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 5/6] always use struct xfs_btree_block instead of short / longform structures
Date: Wed, 17 Sep 2008 10:59:55 +1000	[thread overview]
Message-ID: <20080917005955.GH5811@disturbed> (raw)
In-Reply-To: <20080916173107.GB26187@lst.de>

On Tue, Sep 16, 2008 at 07:31:07PM +0200, Christoph Hellwig wrote:
> On Tue, Sep 16, 2008 at 04:26:16PM +1000, Dave Chinner wrote:
> > On Mon, Sep 15, 2008 at 02:46:57AM +0200, Christoph Hellwig wrote:
> > > Always use the generic xfs_btree_block type instead of the short / long
> > > structures.  Add XFS_BTREE_SBLOCK_LEN / XFS_BTREE_LBLOCK_LEN defines for
> > > the length of a short / long form block.  The rationale for this is that
> > > we will grow more btree block header variants to support CRCs and other
> > > RAS information, and always accessing them through the same datatype
> > > with unions for the short / long form pointers makes implementing this
> > > much easier.
> > .......
> > > @@ -382,16 +382,16 @@ xfs_alloc_fixup_trees(
> > >  	}
> > >  #ifdef DEBUG
> > >  	{
> > > -		xfs_alloc_block_t	*bnoblock;
> > > -		xfs_alloc_block_t	*cntblock;
> > > +		struct xfs_btree_block		*bnoblock;
> > > +		struct xfs_btree_block		*cntblock;
> > 
> > Only need one tab there?
> 
> I think this was aligning to something, but I don't really care.
> 
> > > -			bnoblock = XFS_BUF_TO_ALLOC_BLOCK(bno_cur->bc_bufs[0]);
> > > -			cntblock = XFS_BUF_TO_ALLOC_BLOCK(cnt_cur->bc_bufs[0]);
> > >  			XFS_WANT_CORRUPTED_RETURN(
> > > -				be16_to_cpu(bnoblock->bb_numrecs) ==
> > > -				be16_to_cpu(cntblock->bb_numrecs));
> > > +				bnoblock->bb_numrecs ==
> > > +				cntblock->bb_numrecs);
> > 
> > The comparison could probably be made one line....
> 
> That would be far over 80 characters.

I meant:
			XFS_WANT_CORRUPTED_RETURN(
				bnoblock->bb_numrecs == cntblock->bb_numrecs);

Which doesn't go over 80 chars.

Doesn't really matter, though.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2008-09-17  0:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-15  0:46 [PATCH 5/6] always use struct xfs_btree_block instead of short / longform structures Christoph Hellwig
2008-09-16  6:26 ` Dave Chinner
2008-09-16 17:31   ` Christoph Hellwig
2008-09-17  0:59     ` Dave Chinner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-09-22 11:06 Christoph Hellwig
2008-10-01 15:22 ` 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=20080917005955.GH5811@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