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>
---
 arch/ia64/hp/common/sba_iommu.c | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/arch/ia64/hp/common/sba_iommu.c b/arch/ia64/hp/common/sba_iommu.c
index 656a488..335bf4a 100644
--- a/arch/ia64/hp/common/sba_iommu.c
+++ b/arch/ia64/hp/common/sba_iommu.c
@@ -138,11 +138,7 @@
 #endif
 
 #ifdef ASSERT_PDIR_SANITY
-#define ASSERT(expr) \
-        if(!(expr)) { \
-                printk( "\n" __FILE__ ":%d: Assertion " #expr " 
failed!\n",__LINE__); \
-                panic(#expr); \
-        }
+#define ASSERT(expr) ASSERT_FAIL(expr)
 #else
 #define ASSERT(expr)
 #endif
-- 
1.8.3.1

Reply via email to