public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Mark Brown <broonie@kernel•org>, Liam Girdwood <lgirdwood@gmail•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	Charles Keepax <ckeepax@opensource•wolfsonmicro.com>
Subject: linux-next: build warnings after merge of the sound-asoc tree
Date: Tue, 31 May 2016 11:43:57 +1000	[thread overview]
Message-ID: <20160531114357.5010daa3@canb.auug.org.au> (raw)

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")

-- 
Cheers,
Stephen Rothwell

             reply	other threads:[~2016-05-31  1:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-31  1:43 Stephen Rothwell [this message]
2016-05-31  8:16 ` linux-next: build warnings after merge of the sound-asoc tree Charles Keepax
  -- 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=20160531114357.5010daa3@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=broonie@kernel$(echo .)org \
    --cc=ckeepax@opensource$(echo .)wolfsonmicro.com \
    --cc=lgirdwood@gmail$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    /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