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>
---
net/rxrpc/ar-internal.h | 8 +-------
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/net/rxrpc/ar-internal.h b/net/rxrpc/ar-internal.h
index 6d29a36..b428dc7 100644
--- a/net/rxrpc/ar-internal.h
+++ b/net/rxrpc/ar-internal.h
@@ -1181,13 +1181,7 @@ static inline bool after_eq(u32 seq1, u32 seq2)
*/
#if 1 // defined(__KDEBUGALL)
-#define ASSERT(X) \
-do { \
- if (unlikely(!(X))) { \
- pr_err("Assertion failed\n"); \
- BUG(); \
- } \
-} while (0)
+#define ASSERT(X) ASSERT_FAIL(x)
#define ASSERTCMP(X, OP, Y) \
do { \
--
1.8.3.1
