From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: Intel: Fix sparse warnings for firmware loader.
Date: Wed, 19 Feb 2014 11:06:40 +0000 [thread overview]
Message-ID: <1392808000.2351.40.camel@loki> (raw)
In-Reply-To: <1392807637-4767-1-git-send-email-liam.r.girdwood@linux.intel.com>
On Wed, 2014-02-19 at 11:00 +0000, Liam Girdwood wrote:
> Sparse gives us the following warning on sst-firmware.c
>
> CHECK sound/soc/intel/sst-firmware.c
> sound/soc/intel/sst-firmware.c:39:34: warning: incorrect type in argument 1 (different address spaces)
> sound/soc/intel/sst-firmware.c:39:34: expected void volatile [noderef] <asn:2>*dst
> sound/soc/intel/sst-firmware.c:39:34: got void *
> sound/soc/intel/sst-firmware.c:417:36: warning: incorrect type in argument 1 (different address spaces)
> sound/soc/intel/sst-firmware.c:417:36: expected void *dest
> sound/soc/intel/sst-firmware.c:417:36: got void [noderef] <asn:2>*
> sound/soc/intel/sst-firmware.c:430:5: warning: symbol 'sst_block_module_remove' was not declared. Should it be static?
>
Btw, the last warning appears to be a false positive as
sst_block_module_remove is exported as GPL symbol.
Liam
> This patch removes this warning.
>
> Signed-off-by: Liam Girdwood <liam.r.girdwood@linux.intel.com>
> ---
> sound/soc/intel/sst-firmware.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/sound/soc/intel/sst-firmware.c b/sound/soc/intel/sst-firmware.c
> index 31cd154..dee7eb5 100644
> --- a/sound/soc/intel/sst-firmware.c
> +++ b/sound/soc/intel/sst-firmware.c
> @@ -30,7 +30,7 @@
> #include "sst-dsp.h"
> #include "sst-dsp-priv.h"
>
> -static void sst_memcpy32(void *dest, void *src, u32 bytes)
> +static void sst_memcpy32(volatile void __iomem *dest, void *src, u32 bytes)
> {
> u32 i;
>
next prev parent reply other threads:[~2014-02-19 11:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 11:00 [PATCH] ASoC: Intel: Fix sparse warnings for firmware loader Liam Girdwood
2014-02-19 11:06 ` Liam Girdwood [this message]
2014-02-19 11:10 ` Liam Girdwood
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=1392808000.2351.40.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=tiwai@suse.de \
/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