From: kbuild test robot <lkp@intel.com>
To: Shuming Fan <shumingf@realtek.com>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
kbuild-all@01.org
Subject: [asoc:for-5.3 110/113] sound/soc/codecs/rt1011.c:1291:3: warning: this decimal constant is unsigned only in ISO C90
Date: Tue, 4 Jun 2019 23:30:23 +0800 [thread overview]
Message-ID: <201906042321.Mq1H7nBw%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2595 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.3
head: 9b8e8b893ff52264df2b54a6820ae3c4bb820624
commit: d6e65bb7ff0d360c4c5462c3d0b237f2a07e5312 [110/113] ASoC: rt1011: Add RT1011 amplifier driver
config: xtensa-allyesconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 7.4.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout d6e65bb7ff0d360c4c5462c3d0b237f2a07e5312
# save the attached .config to linux build tree
GCC_VERSION=7.4.0 make.cross ARCH=xtensa
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
sound/soc/codecs/rt1011.c: In function 'rt1011_r0_load_mode_put':
>> sound/soc/codecs/rt1011.c:1291:3: warning: this decimal constant is unsigned only in ISO C90
format = 2147483648; /* 2^24 * 128 */
^~~~~~
sound/soc/codecs/rt1011.c: In function 'rt1011_calibrate':
sound/soc/codecs/rt1011.c:2123:4: warning: this decimal constant is unsigned only in ISO C90
format = 2147483648; /* 2^24 * 128 */
^~~~~~
vim +1291 sound/soc/codecs/rt1011.c
1272
1273 static int rt1011_r0_load_mode_put(struct snd_kcontrol *kcontrol,
1274 struct snd_ctl_elem_value *ucontrol)
1275 {
1276 struct snd_soc_component *component = snd_kcontrol_chip(kcontrol);
1277 struct rt1011_priv *rt1011 = snd_soc_component_get_drvdata(component);
1278 struct device *dev;
1279 unsigned int r0_integer, r0_factor, format;
1280
1281 if (ucontrol->value.integer.value[0] == rt1011->r0_reg)
1282 return 0;
1283
1284 if (!component->card->instantiated)
1285 return 0;
1286
1287 dev = regmap_get_device(rt1011->regmap);
1288 if (snd_soc_component_get_bias_level(component) == SND_SOC_BIAS_OFF) {
1289 rt1011->r0_reg = ucontrol->value.integer.value[0];
1290
> 1291 format = 2147483648; /* 2^24 * 128 */
1292 r0_integer = format / rt1011->r0_reg / 128;
1293 r0_factor = ((format / rt1011->r0_reg * 100) / 128)
1294 - (r0_integer * 100);
1295 dev_info(dev, "New r0 resistance about %d.%02d ohm, reg=0x%X\n",
1296 r0_integer, r0_factor, rt1011->r0_reg);
1297
1298 if (rt1011->r0_reg)
1299 rt1011_r0_load(rt1011);
1300 }
1301
1302 return 0;
1303 }
1304
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 58655 bytes --]
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
reply other threads:[~2019-06-04 15:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201906042321.Mq1H7nBw%lkp@intel.com \
--to=lkp@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kbuild-all@01.org \
--cc=shumingf@realtek.com \
/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).