From: Martin K. Petersen Date: Wed, 29 Oct 2014 02:27:43 +0000 (-0600) Subject: block: Fix merge logic when CONFIG_BLK_DEV_INTEGRITY is not defined X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=cb1a5ab6ece7a37da4ac98ee26b0475b7c3ea79e;p=GitHub%2Fmoto-9609%2Fandroid_kernel_motorola_exynos9610.git block: Fix merge logic when CONFIG_BLK_DEV_INTEGRITY is not defined Commit 4eaf99beadce switched to returning bool and as a result reversed the logic of the integrity merge checks. However, the empty stubs used when the block integrity code is compiled out were still returning 0. Make these stubs return "true". Signed-off-by: Martin K. Petersen Reported-by: Michael L. Semon Tested-by: Michael L. Semon Signed-off-by: Jens Axboe --- diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h index 0207a78a8d82..6cbee8395f60 100644 --- a/include/linux/blkdev.h +++ b/include/linux/blkdev.h @@ -1583,13 +1583,13 @@ static inline bool blk_integrity_merge_rq(struct request_queue *rq, struct request *r1, struct request *r2) { - return 0; + return true; } static inline bool blk_integrity_merge_bio(struct request_queue *rq, struct request *r, struct bio *b) { - return 0; + return true; } static inline bool blk_integrity_is_initialized(struct gendisk *g) {