linux-kernel - [PATCH] block: use NULL instead of 0 for pointer in blkdev.h

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Thu, 13 Feb 2014 18:51:37 +0900
From:	Daeseok Youn <daeseok.youn@...il.com>
To:	akpm@...ux-foundation.org, axboe@...nel.dk
Cc:	hch@...radead.org, kmo@...erainc.com, snitzer@...hat.com,
	JBottomley@...allels.com, ming.m.lin@...el.com,
	j-nomura@...jp.nec.com, linux-kernel@...r.kernel.org
Subject: [PATCH] block: use NULL instead of 0 for pointer in blkdev.h

>From dc82a41842df1e20e8508cea6922882f8b122a50 Mon Sep 17 00:00:00 2001
From: Daeseok Youn <daeseok.youn@...il.com>
Date: Thu, 13 Feb 2014 16:44:58 +0900
Subject: [PATCH] block: use NULL instead of 0 for pointer in blkdev.h

following sparse warning:

include/linux/blkdev.h:1518:16: warning:
 Using plain integer as NULL pointer

Signed-off-by: Daeseok Youn <daeseok.youn@...il.com>
---
 include/linux/blkdev.h |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h
index 8678c43..26b8466 100644
--- a/include/linux/blkdev.h
+++ b/include/linux/blkdev.h
@@ -1515,7 +1515,7 @@ static inline int blk_rq_map_integrity_sg(struct request_queue *q,
 }
 static inline struct blk_integrity *bdev_get_integrity(struct block_device *b)
 {
-	return 0;
+	return NULL;
 }
 static inline struct blk_integrity *blk_get_integrity(struct gendisk *disk)
 {
-- 
1.7.9.5
---

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/