Since ASSERT_FAIL() and ASSERT_WARN() have been provided, ASSERT()
may be realized through them, thus reducing code redundancy and
facilitating problem analysis.
Signed-off-by: Chunguang Xu <broo...@tencent.com>
---
fs/afs/internal.h | 9 +--------
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git a/fs/afs/internal.h b/fs/afs/internal.h
index 792ac71..72594e5 100644
--- a/fs/afs/internal.h
+++ b/fs/afs/internal.h
@@ -1580,14 +1580,7 @@ static inline int afs_bad(struct afs_vnode *vnode, enum
afs_file_error where)
*/
#if 1 // defined(__KDEBUGALL)
-#define ASSERT(X) \
-do { \
- if (unlikely(!(X))) { \
- printk(KERN_ERR "\n"); \
- printk(KERN_ERR "AFS: Assertion failed\n"); \
- BUG(); \
- } \
-} while(0)
+#define ASSERT(X) ASSERT_FAIL(x)
#define ASSERTCMP(X, OP, Y) \
do { \
--
1.8.3.1
