linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amelie DELAUNAY <amelie.delaunay@st.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Mathieu Poirier <mathieu.poirier@linaro.org>
Subject: RE: linux-next: build warning after merge of the rtc tree
Date: Fri, 13 Jan 2017 08:42:00 +0000	[thread overview]
Message-ID: <f7eec548c3214003ac7bf3c94ba70153@SFHDAG3NODE2.st.com> (raw)
In-Reply-To: <20170113141809.4784c004@canb.auug.org.au>

Hi Stephen,

I'm going to send a patch to fix this warning.
Thanks,

Regards,
Amelie

> -----Original Message-----
> From: Stephen Rothwell [mailto:sfr@canb.auug.org.au]
> Sent: vendredi 13 janvier 2017 04:18
> To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
> Cc: linux-next@vger.kernel.org; linux-kernel@vger.kernel.org; Amelie
> DELAUNAY <amelie.delaunay@st.com>; Mathieu Poirier
> <mathieu.poirier@linaro.org>
> Subject: linux-next: build warning after merge of the rtc tree
> 
> Hi Alexandre,
> 
> After merging the rtc tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
> 
> In file included from drivers/rtc/rtc-stm32.c:14:0:
> drivers/rtc/rtc-stm32.c: In function 'stm32_rtc_probe':
> drivers/rtc/rtc-stm32.c:653:51: warning: large integer implicitly truncated to
> unsigned type [-Woverflow]
>   regmap_update_bits(rtc->dbp, PWR_CR, PWR_CR_DBP, ~PWR_CR_DBP);
>                                                    ^
> include/linux/regmap.h:73:42: note: in definition of macro
> 'regmap_update_bits'
>   regmap_update_bits_base(map, reg, mask, val, NULL, false, false)
>                                           ^
> drivers/rtc/rtc-stm32.c: In function 'stm32_rtc_remove':
> drivers/rtc/rtc-stm32.c:675:51: warning: large integer implicitly truncated to
> unsigned type [-Woverflow]
>   regmap_update_bits(rtc->dbp, PWR_CR, PWR_CR_DBP, ~PWR_CR_DBP);
>                                                    ^
> include/linux/regmap.h:73:42: note: in definition of macro
> 'regmap_update_bits'
>   regmap_update_bits_base(map, reg, mask, val, NULL, false, false)
>                                           ^
> 
> Introduced by commit
> 
>   4e64350f42e2 ("rtc: add STM32 RTC driver")
> 
> --
> Cheers,
> Stephen Rothwell

  reply	other threads:[~2017-01-13  8:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-13  3:18 linux-next: build warning after merge of the rtc tree Stephen Rothwell
2017-01-13  8:42 ` Amelie DELAUNAY [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-03-23  5:24 Stephen Rothwell
2020-03-17  5:30 Stephen Rothwell
2019-10-30  4:41 Stephen Rothwell
2019-11-08  5:29 ` Stephen Rothwell
2019-11-08 15:20   ` Alexandre Belloni
2019-08-21  6:31 Stephen Rothwell
2019-03-28  1:23 Stephen Rothwell
2019-03-28  1:36 ` Joel Stanley
2019-03-28  1:57   ` Alexandre Belloni
2019-03-28  2:09     ` Joel Stanley
2018-03-21  6:44 Stephen Rothwell
2017-07-06  4:24 Stephen Rothwell
2017-07-06  5:54 ` Heiner Kallweit
2017-07-06  6:59   ` Alexandre Belloni
2017-06-29  5:42 Stephen Rothwell
2017-01-10  3:01 Stephen Rothwell
2017-01-10 10:59 ` Alexandre Belloni
2016-07-11  8:12 Stephen Rothwell
2016-07-11  8:23 ` Uwe Kleine-König
2016-07-11 21:23   ` Alexandre Belloni

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=f7eec548c3214003ac7bf3c94ba70153@SFHDAG3NODE2.st.com \
    --to=amelie.delaunay@st.com \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).