[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <5e7c145a8b5a57c78b9228806738ccb0cfc2ac98.1598518912.git.brookxu@tencent.com>
Date: Thu, 27 Aug 2020 18:14:11 +0800
From: Chunguang Xu <brookxu.cn@...il.com>
To: arnd@...db.de
Cc: rppt@...nel.org, linux-arch@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: [PATCH 06/23] rxrpc: use ASSERT_FAIL()/ASSERT_WARN() to cleanup some code
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 <brookxu@...cent.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
Powered by blists - more mailing lists