linux-kernel - Re: [PATCH] staging/vt6656: Fix too large integer constant warning on 32-bit

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>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <201303042059.13394.PeterHuewe@gmx.de>
Date:	Mon, 4 Mar 2013 20:59:13 +0100
From:	Peter Hüwe <PeterHuewe@....de>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	"Greg Kroah-Hartman" <gregkh@...uxfoundation.org>,
	Fengguang Wu <fengguang.wu@...el.com>,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging/vt6656: Fix too large integer constant warning on 32-bit

Am Montag, 4. März 2013, 20:42:00 schrieb Geert Uytterhoeven:
> drivers/staging/vt6656/card.c: In function ‘CARDqGetNextTBTT’:
> drivers/staging/vt6656/card.c:793: warning: integer constant is too large
> for ‘unsigned long’ type
> 
> Commit c7b7cad0d8df823ea063c86a54316bbcbfa04a7c ("staging/vt6656: Fix
> sparse warning constant 0xffffffff00000000U is so big it is unsigned long")
> changed the constant to "0xffffffff00000000UL", but that only works on
> 64-bit.  Change it "0xffffffff00000000ULL" to fix it for 32-bit, too.
> 
Thanks - sorry that I had missed this.
I thought I had it compiled on x86 (non64 bit), too.

Reviewed-by: Peter Huewe <peterhuewe@....de>
--
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/