From: Christoph Hellwig <hch@lst.de>
To: xfs@oss.sgi.com
Subject: [PATCH 6/8] xfsprogs: remove boolean_t typedef
Date: Sun, 21 Jun 2015 11:22:02 +0200 [thread overview]
Message-ID: <1434878524-18176-7-git-send-email-hch@lst.de> (raw)
In-Reply-To: <1434878524-18176-1-git-send-email-hch@lst.de>
Only one use of this exists, and it's treated like an int anyway by
both caller and callee.
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
include/darwin.h | 3 ---
include/freebsd.h | 2 --
include/gnukfreebsd.h | 2 --
include/linux.h | 5 -----
logprint/log_misc.c | 2 +-
5 files changed, 1 insertion(+), 13 deletions(-)
diff --git a/include/darwin.h b/include/darwin.h
index ca9f8f4..3655d40 100644
--- a/include/darwin.h
+++ b/include/darwin.h
@@ -144,9 +144,6 @@ typedef char* xfs_caddr_t;
#define O_SYNC 0
#endif
-#define B_FALSE 0
-#define B_TRUE 1
-
#define ENOATTR 989 /* Attribute not found */
#define EFSCORRUPTED 990 /* Filesystem is corrupted */
#define EFSBADCRC 991 /* Bad CRC detected */
diff --git a/include/freebsd.h b/include/freebsd.h
index d01c0c1..244b012 100644
--- a/include/freebsd.h
+++ b/include/freebsd.h
@@ -55,8 +55,6 @@ typedef __int64_t xfs_daddr_t;
typedef char* xfs_caddr_t;
typedef off_t loff_t;
-typedef enum { B_FALSE,B_TRUE } boolean_t;
-
#define O_LARGEFILE 0
#define HAVE_FID 1
diff --git a/include/gnukfreebsd.h b/include/gnukfreebsd.h
index e92858d..978a257 100644
--- a/include/gnukfreebsd.h
+++ b/include/gnukfreebsd.h
@@ -45,8 +45,6 @@ typedef __int64_t xfs_daddr_t;
typedef char* xfs_caddr_t;
typedef off_t loff_t;
-typedef enum { B_FALSE,B_TRUE } boolean_t;
-
#define HAVE_FID 1
static __inline__ int xfsctl(const char *path, int fd, int cmd, void *p)
diff --git a/include/linux.h b/include/linux.h
index da50421..e7a3cb2 100644
--- a/include/linux.h
+++ b/include/linux.h
@@ -144,9 +144,4 @@ typedef __uint32_t xfs_dev_t;
typedef __int64_t xfs_daddr_t;
typedef char* xfs_caddr_t;
-#ifndef _BOOLEAN_T_DEFINED
-typedef enum {B_FALSE, B_TRUE} boolean_t;
-#define _BOOLEAN_T_DEFINED 1
-#endif
-
#endif /* __XFS_LINUX_H__ */
diff --git a/logprint/log_misc.c b/logprint/log_misc.c
index 6f41c91..708a513 100644
--- a/logprint/log_misc.c
+++ b/logprint/log_misc.c
@@ -641,7 +641,7 @@ xlog_print_trans_inode(
int len,
int *i,
int num_ops,
- boolean_t continued)
+ int continued)
{
xfs_icdinode_t dino;
xlog_op_header_t *op_head;
--
1.9.1
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-06-21 9:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-21 9:21 typedef cleanups for xfsprogs Christoph Hellwig
2015-06-21 9:21 ` [PATCH 1/8] xfsprogs: remove register keywords Christoph Hellwig
2015-06-21 9:21 ` [PATCH 2/8] xfsprogs: remove __psint_t and __psunsigned_t Christoph Hellwig
2015-06-23 5:42 ` Dave Chinner
2015-06-21 9:21 ` [PATCH 3/8] xfsprogs: remove the unused inst_t typedef Christoph Hellwig
2015-06-21 9:22 ` [PATCH 4/8] xfsprogs: remove the uint_t typedef Christoph Hellwig
2015-06-21 9:22 ` [PATCH 5/8] xfsprogs: remove the uchar_t typedef Christoph Hellwig
2015-06-21 9:22 ` Christoph Hellwig [this message]
2015-06-21 9:22 ` [PATCH 7/8] xfsprogs: remove non-Linux defintions for loff_t Christoph Hellwig
2015-06-21 9:22 ` [PATCH 8/8] xfsprogs: remove xfs_caddr_t 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=1434878524-18176-7-git-send-email-hch@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