From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Maxime Coquelin <mcoquelin.stm32@gmail.com>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, fengguang.wu@intel.com
Subject: Re: [PATCH] clockevents: timer-stm32: Fix build warning spotted by kbuild test robot
Date: Thu, 28 May 2015 00:52:14 +0200 [thread overview]
Message-ID: <20150527225213.GA4001@macpro.local> (raw)
In-Reply-To: <1432744883-30070-1-git-send-email-mcoquelin.stm32@gmail.com>
On Wed, May 27, 2015 at 06:41:23PM +0200, Maxime Coquelin wrote:
> This patch fixes below warning spotted by kbuild test robot when building
> with ARCH=powerpc:
>
> drivers/clocksource/timer-stm32.c: In function 'stm32_clockevent_init':
> >> drivers/clocksource/timer-stm32.c:140:9: warning: large integer implicitly truncated to unsigned type [-Woverflow]
> writel_relaxed(~0UL, data->base + TIM_ARR);
>
> The fix consists in casting the value to u32.
>
> Reported-by: kbuild test robot <fengguang.wu@intel.com>
> Signed-off-by: Maxime Coquelin <mcoquelin.stm32@gmail.com>
> ---
> drivers/clocksource/timer-stm32.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/clocksource/timer-stm32.c b/drivers/clocksource/timer-stm32.c
> index fad2e2e..c9578d8 100644
> --- a/drivers/clocksource/timer-stm32.c
> +++ b/drivers/clocksource/timer-stm32.c
> @@ -137,7 +137,7 @@ static void __init stm32_clockevent_init(struct device_node *np)
> }
>
> /* Detect whether the timer is 16 or 32 bits */
> - writel_relaxed(~0UL, data->base + TIM_ARR);
> + writel_relaxed((u32)~0UL, data->base + TIM_ARR);
> max_delta = readl_relaxed(data->base + TIM_ARR);
> if (max_delta == ~0UL) {
> prescaler = 1;
Since the warning come from using a unsigned long constant while
writel() expect an unsigned int, why not simply use ~0U ?
Luc Van Oostenryck
next prev parent reply other threads:[~2015-05-27 22:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 16:41 [PATCH] clockevents: timer-stm32: Fix build warning spotted by kbuild test robot Maxime Coquelin
2015-05-27 22:52 ` Luc Van Oostenryck [this message]
2015-05-28 5:03 ` Maxime Coquelin
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=20150527225213.GA4001@macpro.local \
--to=luc.vanoostenryck@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.