From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>, <linux-next@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the sound-asoc tree
Date: Tue, 31 May 2016 09:16:26 +0100 [thread overview]
Message-ID: <20160531081626.GI20422@localhost.localdomain> (raw)
In-Reply-To: <20160531114357.5010daa3@canb.auug.org.au>
On Tue, May 31, 2016 at 11:43:57AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the sound-asoc tree, today's linux-next build (x86_64
> allmodconfig) produced these warnings:
>
> sound/soc/codecs/cs47l24.c: In function 'cs47l24_adsp2_irq'
> :
> sound/soc/codecs/cs47l24.c:1091:13: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
> (void *)i);
> ^
> sound/soc/codecs/wm5110.c: In function 'wm5110_adsp2_irq':
> sound/soc/codecs/wm5110.c:2246:13: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
> (void *)i);
> ^
>
> Introduced by commit
>
> 7baa7e2490e1 ("ASoC: arizona: Add event notification on voice trigger events")
Apologies I will get a fix out today.
Thanks,
Charles
next prev parent reply other threads:[~2016-05-31 8:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 1:43 linux-next: build warnings after merge of the sound-asoc tree Stephen Rothwell
2016-05-31 8:16 ` Charles Keepax [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-08-16 1:36 Stephen Rothwell
2012-04-20 4:28 Stephen Rothwell
2012-04-23 9:35 ` Liam Girdwood
2011-04-12 2:05 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=20160531081626.GI20422@localhost.localdomain \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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