dm crypt: Fix sparse complaints
authorBart Van Assche <bart.vanassche@sandisk.com>
Tue, 28 Jun 2016 14:32:32 +0000 (16:32 +0200)
committerMike Snitzer <snitzer@redhat.com>
Fri, 1 Jul 2016 14:53:21 +0000 (10:53 -0400)
Avoid that sparse complains about assigning a __le64 value to a u64
variable.  Remove the (u64) casts since these are superfluous.  This
patch does not change the behavior of the source code.

Signed-off-by: Bart Van Assche <bart.vanassche@sandisk.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
drivers/md/dm-crypt.c

index 96dd5d7e454ac01a5c062f1f30a4d5294be2822c..8f2e3e2ffd26aaac40ccec04f9257d65ed2d962d 100644 (file)
@@ -683,7 +683,7 @@ static int crypt_iv_tcw_whitening(struct crypt_config *cc,
                                  u8 *data)
 {
        struct iv_tcw_private *tcw = &cc->iv_gen_private.tcw;
-       u64 sector = cpu_to_le64((u64)dmreq->iv_sector);
+       __le64 sector = cpu_to_le64(dmreq->iv_sector);
        u8 buf[TCW_WHITENING_SIZE];
        SHASH_DESC_ON_STACK(desc, tcw->crc32_tfm);
        int i, r;
@@ -722,7 +722,7 @@ static int crypt_iv_tcw_gen(struct crypt_config *cc, u8 *iv,
                            struct dm_crypt_request *dmreq)
 {
        struct iv_tcw_private *tcw = &cc->iv_gen_private.tcw;
-       u64 sector = cpu_to_le64((u64)dmreq->iv_sector);
+       __le64 sector = cpu_to_le64(dmreq->iv_sector);
        u8 *src;
        int r = 0;