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/video/fbdev/cirrusfb.c | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/drivers/video/fbdev/cirrusfb.c b/drivers/video/fbdev/cirrusfb.c index 3df64a9..3dcafdd 100644 --- a/drivers/video/fbdev/cirrusfb.c +++ b/drivers/video/fbdev/cirrusfb.c @@ -67,11 +67,7 @@ /* debugging assertions */ #ifndef CIRRUSFB_NDEBUG -#define assert(expr) \ - if (!(expr)) { \ - printk("Assertion failed! %s,%s,%s,line=%d\n", \ - #expr, __FILE__, __func__, __LINE__); \ - } +#define assert(expr) ASSERT_WARN(expr) #else #define assert(expr) #endif -- 1.8.3.1