From: Timothy Shimmin <tes@sgi.com>
To: Christoph Hellwig <hch@lst.de>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 02/15] use the same btree_cur union member for alloc and inobt trees
Date: Tue, 29 Jul 2008 13:55:03 +1000 [thread overview]
Message-ID: <488E9497.2090900@sgi.com> (raw)
In-Reply-To: <20080723200826.GC7401@lst.de>
Hi there,
This was fine but just one thing which looked odd:
Christoph Hellwig wrote:
>
> Index: linux-2.6-xfs/fs/xfs/xfs_btree.c
> ===================================================================
> --- linux-2.6-xfs.orig/fs/xfs/xfs_btree.c 2008-07-16 03:24:18.000000000 +0200
> +++ linux-2.6-xfs/fs/xfs/xfs_btree.c 2008-07-16 03:24:19.000000000 +0200
> @@ -570,6 +570,13 @@ xfs_btree_init_cursor(
> cur->bc_private.a.agbp = agbp;
> cur->bc_private.a.agno = agno;
> break;
> + case XFS_BTNUM_INO:
> + /*
> + * Inode allocation btree fields.
> + */
> + cur->bc_private.a.agbp = agbp;
> + cur->bc_private.a.agno = agno;
> + break;
> case XFS_BTNUM_BMAP:
> /*
> * Bmap btree fields.
> @@ -582,13 +589,6 @@ xfs_btree_init_cursor(
> cur->bc_private.b.flags = 0;
> cur->bc_private.b.whichfork = whichfork;
> break;
> - case XFS_BTNUM_INO:
> - /*
> - * Inode allocation btree fields.
> - */
> - cur->bc_private.i.agbp = agbp;
> - cur->bc_private.i.agno = agno;
> - break;
> default:
Could probably just add XFS_BNUM_INO to the case below
(and modify the comment):
> case XFS_BTNUM_BNO:
> case XFS_BTNUM_CNT:
> /*
> * Allocation btree fields.
> */
> cur->bc_private.a.agbp = agbp;
> cur->bc_private.a.agno = agno;
> break;
--Tim
next prev parent reply other threads:[~2008-07-29 3:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 20:08 [PATCH 02/15] use the same btree_cur union member for alloc and inobt trees Christoph Hellwig
2008-07-29 3:55 ` Timothy Shimmin [this message]
2008-07-29 4:07 ` Christoph Hellwig
2008-07-29 4:12 ` Timothy Shimmin
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=488E9497.2090900@sgi.com \
--to=tes@sgi.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