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@xxxxxxxxxxx> --- drivers/atm/fore200e.c | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/drivers/atm/fore200e.c b/drivers/atm/fore200e.c index a81bc49..04f121b 100644 --- a/drivers/atm/fore200e.c +++ b/drivers/atm/fore200e.c @@ -83,11 +83,7 @@ #define FORE200E_NEXT_ENTRY(index, modulo) (index = ((index) + 1) % (modulo)) #if 1 -#define ASSERT(expr) if (!(expr)) { \ - printk(FORE200E "assertion failed! %s[%d]: %s\n", \ - __func__, __LINE__, #expr); \ - panic(FORE200E "%s", __func__); \ - } +#define ASSERT(expr) ASSERT_FAIL(expr) #else #define ASSERT(expr) do {} while (0) #endif -- 1.8.3.1