From: Christoph Hellwig <hch@lst.de>
To: xfs@oss.sgi.com
Subject: [PATCH 1/6] fix up btree headers for userspace
Date: Mon, 22 Sep 2008 13:06:26 +0200 [thread overview]
Message-ID: <20080922110626.GB26007@lst.de> (raw)
[-- Attachment #1: xfs-btree-header-fixes --]
[-- Type: text/plain, Size: 1342 bytes --]
Remove two __KERNEL__ sections in xfs_bmap_btree.h and xfs_btree.h that
prevent using the new generic btree code in xfsprogs.
Signed-off-by: Christoph Hellwig <hch@lst.de>
--- linux-2.6-xfs/fs/xfs/xfs_bmap_btree.h 2008-08-31 23:17:27.000000000 -0300
+++ linux-2.6-xfs/fs/xfs/xfs_bmap_btree.h 2008-08-31 23:17:57.000000000 -0300
@@ -231,8 +231,6 @@ typedef struct xfs_btree_lblock xfs_bmbt
be16_to_cpu((bb)->bb_numrecs) <= (mp)->m_bmap_dmxr[(level) != 0])
-#ifdef __KERNEL__
-
/*
* Prototypes for xfs_bmap.c to call.
*/
@@ -264,6 +262,5 @@ extern void xfs_bmbt_to_bmdr(xfs_bmbt_bl
extern struct xfs_btree_cur *xfs_bmbt_init_cursor(struct xfs_mount *,
struct xfs_trans *, struct xfs_inode *, int);
-#endif /* __KERNEL__ */
#endif /* __XFS_BMAP_BTREE_H__ */
--- linux-2.6-xfs/fs/xfs/xfs_btree.h 2008-08-31 23:12:32.000000000 -0300
+++ linux-2.6-xfs/fs/xfs/xfs_btree.h 2008-08-31 23:12:46.000000000 -0300
@@ -327,8 +327,6 @@ typedef struct xfs_btree_cur
#define XFS_BUF_TO_SBLOCK(bp) ((xfs_btree_sblock_t *)XFS_BUF_PTR(bp))
-#ifdef __KERNEL__
-
/*
* Check that long form block header is ok.
*/
@@ -515,8 +513,6 @@ static inline int xfs_btree_get_level(st
return be16_to_cpu(block->bb_level);
}
-#endif /* __KERNEL__ */
-
/*
* Min and max functions for extlen, agblock, fileoff, and filblks types.
--
next reply other threads:[~2008-09-22 11:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 11:06 Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-15 0:46 [PATCH 1/6] fix up btree headers for userspace Christoph Hellwig
2008-09-16 5:12 ` Dave Chinner
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=20080922110626.GB26007@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