From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Mark Brown <broonie@kernel•org>, Liam Girdwood <lgirdwood@gmail•com>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Saravanan Sekar <sravanhome@gmail•com>
Subject: linux-next: build warning after merge of the regulator tree
Date: Fri, 10 Jan 2020 13:41:19 +1100 [thread overview]
Message-ID: <20200110134119.0fa47da8@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 777 bytes --]
Hi all,
After merging the regulator tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
In file included from drivers/regulator/mpq7920.c:19:
drivers/regulator/mpq7920.c: In function 'mpq7920_parse_cb':
drivers/regulator/mpq7920.c:224:13: warning: conversion from 'long unsigned int' to 'unsigned int' changes value from '18446744073709551551' to '4294967231' [-Woverflow]
224 | BIT(6), ~BIT(6));
include/linux/regmap.h:75:42: note: in definition of macro 'regmap_update_bits'
75 | regmap_update_bits_base(map, reg, mask, val, NULL, false, false)
| ^~~
Introduced by commit
6501c1f54a17 ("regulator: mpq7920: add mpq7920 regulator driver")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-01-10 2:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 2:41 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-23 4:52 linux-next: build warning after merge of the regulator tree Stephen Rothwell
2024-10-23 4:51 Stephen Rothwell
2018-10-02 3:07 Stephen Rothwell
2018-10-02 6:16 ` Matti Vaittinen
2018-10-02 6:25 ` Stephen Rothwell
2018-10-02 6:43 ` Matti Vaittinen
2018-10-02 13:02 ` Mark Brown
2016-04-18 3:43 Stephen Rothwell
2016-04-18 9:15 ` Mark Brown
2015-10-07 2:45 Stephen Rothwell
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=20200110134119.0fa47da8@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=broonie@kernel$(echo .)org \
--cc=lgirdwood@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sravanhome@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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