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>
---
 drivers/net/ethernet/hisilicon/hns/hnae.h | 8 +-------
 1 file changed, 1 insertion(+), 7 deletions(-)

diff --git a/drivers/net/ethernet/hisilicon/hns/hnae.h 
b/drivers/net/ethernet/hisilicon/hns/hnae.h
index 6ab9458..55710f4 100644
--- a/drivers/net/ethernet/hisilicon/hns/hnae.h
+++ b/drivers/net/ethernet/hisilicon/hns/hnae.h
@@ -41,13 +41,7 @@
 #ifdef DEBUG
 
 #ifndef assert
-#define assert(expr) \
-do { \
-       if (!(expr)) { \
-               pr_err("Assertion failed! %s, %s, %s, line %d\n", \
-                          #expr, __FILE__, __func__, __LINE__); \
-       } \
-} while (0)
+#define assert(expr) ASSERT_WARN(expr)
 #endif
 
 #else
-- 
1.8.3.1

Reply via email to