Messages in this thread Patch in this message | | | From | Chunguang Xu <> | Subject | [PATCH 15/23] media/staging: use ASSERT_FAIL()/ASSERT_WARN() to cleanup some code | Date | Thu, 27 Aug 2020 18:14:20 +0800 |
| |
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@tencent.com> --- .../staging/media/atomisp/pci/hive_isp_css_include/assert_support.h | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/drivers/staging/media/atomisp/pci/hive_isp_css_include/assert_support.h b/drivers/staging/media/atomisp/pci/hive_isp_css_include/assert_support.h index 7382c0b..c7e65e3 100644 --- a/drivers/staging/media/atomisp/pci/hive_isp_css_include/assert_support.h +++ b/drivers/staging/media/atomisp/pci/hive_isp_css_include/assert_support.h @@ -51,11 +51,7 @@ * but that causes many compiler warnings (==errors) under Android * because it seems that the BUG_ON() macro is not seen as a check by * gcc like the BUG() macro is. */ -#define assert(cnd) \ - do { \ - if (!(cnd)) \ - BUG(); \ - } while (0) +#define assert(cnd) ASSERT_FAIL(cnd) #ifndef PIPE_GENERATION /* Deprecated OP___assert, this is still used in ~1000 places -- 1.8.3.1
| |