From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Mark Brown <broonie@kernel•org>, Lee Jones <lee.jones@linaro•org>,
Liam Girdwood <lgirdwood@gmail•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Richard Fitzgerald <rf@opensource•wolfsonmicro.com>,
Nariman Poushin <nariman@opensource•wolfsonmicro.com>,
Charles Keepax <ckeepax@opensource•wolfsonmicro.com>
Subject: linux-next: build warnings after merge of the regmap tree
Date: Fri, 17 Jul 2015 14:39:34 +1000 [thread overview]
Message-ID: <20150717143934.4f0ce5d7@canb.auug.org.au> (raw)
Hi Mark,
After merging the regmap tree, today's linux-next build (powerpc
allyesconfig) produced these warnings:
sound/soc/codecs/wm5110.c: In function 'wm5110_hp_pre_enable':
sound/soc/codecs/wm5110.c:294:9: warning: passing argument 2 of 'regmap_multi_reg_write' from incompatible pointer type
return regmap_multi_reg_write(arizona->regmap, wseq, nregs);
^
In file included from sound/soc/codecs/wm5110.c:19:0:
include/linux/regmap.h:427:5: note: expected 'const struct reg_sequence *' but argument is of type 'const struct reg_default *'
int regmap_multi_reg_write(struct regmap *map, const struct reg_sequence *regs,
^
sound/soc/codecs/wm5110.c: In function 'wm5110_clear_pga_volume':
sound/soc/codecs/wm5110.c:362:8: warning: passing argument 2 of 'regmap_multi_reg_write_bypassed' from incompatible pointer type
ret = regmap_multi_reg_write_bypassed(arizona->regmap, &clear_pga, 1);
^
In file included from sound/soc/codecs/wm5110.c:19:0:
include/linux/regmap.h:429:5: note: expected 'const struct reg_sequence *' but argument is of type 'struct reg_default *'
int regmap_multi_reg_write_bypassed(struct regmap *map,
^
drivers/mfd/wm5110-tables.c: In function 'wm5110_patch':
drivers/mfd/wm5110-tables.c:279:10: warning: passing argument 2 of 'regmap_register_patch' from incompatible pointer type
return regmap_register_patch(arizona->regmap,
^
In file included from include/linux/mfd/arizona/core.h:17:0,
from drivers/mfd/wm5110-tables.c:15:
include/linux/regmap.h:469:5: note: expected 'const struct reg_sequence *' but argument is of type 'const struct reg_default *'
int regmap_register_patch(struct regmap *map, const struct reg_sequence *regs,
^
drivers/mfd/wm8998-tables.c: In function 'wm8998_patch':
drivers/mfd/wm8998-tables.c:48:9: warning: passing argument 2 of 'regmap_register_patch' from incompatible pointer type
return regmap_register_patch(arizona->regmap,
^
In file included from include/linux/mfd/arizona/core.h:17:0,
from drivers/mfd/wm8998-tables.c:15:
include/linux/regmap.h:469:5: note: expected 'const struct reg_sequence *' but argument is of type 'const struct reg_default *'
int regmap_register_patch(struct regmap *map, const struct reg_sequence *regs,
^
Introduced by commit
8019ff6cfc04 ("regmap: Use reg_sequence for multi_reg_write / register_patch")
interacting with commit
561629755a21 ("mfd: arizona: Add support for WM8998 and WM1814")
from the mfd tree and commits
d1acd31883d7 ("ASoC: wm5110: Add special DRE on/off handling for the headphone path")
81207880cef2 ("mfd: wm5110: Add register patch for rev E and above")
from the sound-asoc tree.
I may make up a merge fix for these on Monday ... I love API changes :-(
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
next reply other threads:[~2015-07-17 4:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 4:39 Stephen Rothwell [this message]
2015-07-17 9:44 ` linux-next: build warnings after merge of the regmap tree Nariman Poushin
2015-07-17 10:34 ` Mark Brown
2015-07-17 14:09 ` [PATCH 1/2] mfd: Fixup clients of multi_reg_write/register_patch Nariman Poushin
2015-07-17 17:57 ` Mark Brown
2015-07-20 1:59 ` Stephen Rothwell
2015-09-05 14:08 ` Geert Uytterhoeven
2015-09-18 3:50 ` Stephen Rothwell
2015-09-18 8:33 ` Charles Keepax
2015-09-18 10:25 ` Mark Brown
2015-07-17 14:11 ` [PATCH 2/2] ASoC: wm5110: Use reg_sequence for multi_reg_write/register_patch Nariman Poushin
2015-07-17 15:29 ` linux-next: build warnings after merge of the regmap tree Nariman Poushin
2015-07-17 16:45 ` Charles Keepax
-- strict thread matches above, loose matches on Subject: below --
2013-03-27 4:47 Stephen Rothwell
2013-03-27 10:24 ` Mark Brown
2013-03-27 10:35 ` Stephen Rothwell
2011-08-09 3:21 Stephen Rothwell
2011-08-09 15:01 ` Mark Brown
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=20150717143934.4f0ce5d7@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=broonie@kernel$(echo .)org \
--cc=ckeepax@opensource$(echo .)wolfsonmicro.com \
--cc=lee.jones@linaro$(echo .)org \
--cc=lgirdwood@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=nariman@opensource$(echo .)wolfsonmicro.com \
--cc=rf@opensource$(echo .)wolfsonmicro.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