From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753143AbbKQJhq (ORCPT ); Tue, 17 Nov 2015 04:37:46 -0500 Received: from mail-wm0-f42.google.com ([74.125.82.42]:36876 "EHLO mail-wm0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752808AbbKQJhn (ORCPT ); Tue, 17 Nov 2015 04:37:43 -0500 Subject: Re: [PATCH] clocksource: fsl: avoid harmless 64-bit warnings To: Arnd Bergmann References: <3990834.xnjhm37Grs@wuerfel> Cc: Thomas Gleixner , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Xiubo Li , Shawn Guo , Sascha Hauer , Stefan Agner From: Daniel Lezcano Message-ID: <564AF564.6080406@linaro.org> Date: Tue, 17 Nov 2015 10:37:40 +0100 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <3990834.xnjhm37Grs@wuerfel> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/16/2015 05:34 PM, Arnd Bergmann wrote: > The ftm_clockevent_init passes the value of "~0UL" into a function > that takes a 32-bit argument, which drops the upper 32 bits, as > gcc warns about on ARM64: > > clocksource/fsl_ftm_timer.c: In function 'ftm_clockevent_init': > clocksource/fsl_ftm_timer.c:206:13: warning: large integer implicitly truncated to unsigned type [-Woverflow] > > This was obviously unintended behavior, and is easily avoided by > using '~0u' as the integer literal, because that is 32-bit wide > on all architectures. > > Signed-off-by: Arnd Bergmann Thanks Arnd for the fix. I will apply it on top of branch.