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/block/skd_main.c | 8 +-------
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/drivers/block/skd_main.c b/drivers/block/skd_main.c
index 3a476dc..b5b51e0 100644
--- a/drivers/block/skd_main.c
+++ b/drivers/block/skd_main.c
@@ -41,13 +41,7 @@
static int skd_dbg_level;
static int skd_isr_comp_limit = 4;
-#define SKD_ASSERT(expr) \
- do { \
- if (unlikely(!(expr))) { \
- pr_err("Assertion failed! %s,%s,%s,line=%d\n", \
- # expr, __FILE__, __func__, __LINE__); \
- } \
- } while (0)
+#define SKD_ASSERT(expr) ASSERT_WARN(expr)
#define DRV_NAME "skd"
#define PFX DRV_NAME ": "
--
1.8.3.1
