From: kbuild test robot <lkp@intel.com>
To: Ben Zhang <benzh@chromium.org>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
kbuild-all@lists.01.org,
Curtis Malainey <cujomalainey@chromium.org>
Subject: [alsa-devel] [asoc:for-5.5 160/172] sound/soc/codecs/rt5677-spi.c:148:33: sparse: sparse: Using plain integer as NULL pointer
Date: Thu, 24 Oct 2019 09:07:33 +0800 [thread overview]
Message-ID: <201910240927.cIw8uUAi%lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.5
head: 175fc928198236037174e5c5c066fe3c4691903e
commit: a0e0d135427cf699fe2dee77da0924e0b47f3170 [160/172] ASoC: rt5677: Add a PCM device for streaming hotword via SPI
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-dirty
git checkout a0e0d135427cf699fe2dee77da0924e0b47f3170
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> sound/soc/codecs/rt5677-spi.c:148:33: sparse: sparse: Using plain integer as NULL pointer
>> sound/soc/codecs/rt5677-spi.c:365:13: sparse: sparse: symbol 'rt5677_spi_pcm_page' was not declared. Should it be static?
vim +148 sound/soc/codecs/rt5677-spi.c
139
140 static int rt5677_spi_hw_free(
141 struct snd_soc_component *component,
142 struct snd_pcm_substream *substream)
143 {
144 struct rt5677_dsp *rt5677_dsp =
145 snd_soc_component_get_drvdata(component);
146
147 mutex_lock(&rt5677_dsp->dma_lock);
> 148 rt5677_dsp->substream = 0;
149 mutex_unlock(&rt5677_dsp->dma_lock);
150
151 return snd_pcm_lib_free_vmalloc_buffer(substream);
152 }
153
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
reply other threads:[~2019-10-24 1:09 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=201910240927.cIw8uUAi%lkp@intel.com \
--to=lkp@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=benzh@chromium.org \
--cc=broonie@kernel.org \
--cc=cujomalainey@chromium.org \
--cc=kbuild-all@lists.01.org \
/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