From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: kernel@pengutronix.de, mingo@kernel.org, tglx@linutronix.de,
linux-kernel@vger.kernel.org, Li.Xiubo@freescale.com,
shawnguo@kernel.org, hpa@zytor.com, arnd@arndb.de,
stefan@agner.ch, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:timers/urgent] clocksource/fsl: Avoid harmless 64-bit warnings
Date: Tue, 17 Nov 2015 12:25:26 +0100 [thread overview]
Message-ID: <564B0EA6.708@linaro.org> (raw)
In-Reply-To: <tip-dde7632ed02382e4bac2b57c66ee2285764f2cd7@git.kernel.org>
On 11/17/2015 11:36 AM, tip-bot for Arnd Bergmann wrote:
> Commit-ID: dde7632ed02382e4bac2b57c66ee2285764f2cd7
> Gitweb: http://git.kernel.org/tip/dde7632ed02382e4bac2b57c66ee2285764f2cd7
> Author: Arnd Bergmann <arnd@arndb.de>
> AuthorDate: Mon, 16 Nov 2015 17:34:50 +0100
> Committer: Thomas Gleixner <tglx@linutronix.de>
> CommitDate: Mon, 16 Nov 2015 19:07:08 +0100
>
> clocksource/fsl: Avoid harmless 64-bit warnings
>
> 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 <arnd@arndb.de>
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: Xiubo Li <Li.Xiubo@freescale.com>
> Cc: Shawn Guo <shawnguo@kernel.org>
> Cc: Sascha Hauer <kernel@pengutronix.de>
> Cc: Stefan Agner <stefan@agner.ch>
> Cc: Daniel Lezcano <daniel.lezcano@linaro.org>
> Link: http://lkml.kernel.org/r/3990834.xnjhm37Grs@wuerfel
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
>
> ---
Ok, I dropped the patch from my tree.
-- Daniel
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2015-11-17 11:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 16:34 [PATCH] clocksource: fsl: avoid harmless 64-bit warnings Arnd Bergmann
2015-11-17 9:37 ` Daniel Lezcano
2015-11-17 10:36 ` [tip:timers/urgent] clocksource/fsl: Avoid " tip-bot for Arnd Bergmann
2015-11-17 11:25 ` Daniel Lezcano [this message]
2015-11-17 11:36 ` Thomas Gleixner
2015-11-17 11:43 ` Daniel Lezcano
2015-11-17 11:45 ` Daniel Lezcano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=564B0EA6.708@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=Li.Xiubo@freescale.com \
--cc=arnd@arndb.de \
--cc=hpa@zytor.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=shawnguo@kernel.org \
--cc=stefan@agner.ch \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox