From: kbuild test robot <fengguang.wu@intel.com>
To: Katsuhiro Suzuki <suzuki.katsuhiro@socionext.com>
Cc: kbuild-all@01.org, alsa-devel@alsa-project.org,
Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [asoc:topic/uniphier 3/7] sound/soc/uniphier/aio-core.c:907:5: sparse: symbol 'aiodma_rb_get_rp' was not declared. Should it be static?
Date: Tue, 13 Feb 2018 01:53:10 +0800 [thread overview]
Message-ID: <201802130150.A223WMAh%fengguang.wu@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git topic/uniphier
head: db4cb3d04eba91db48da0032c44b83ed7185973c
commit: f37fe2f9987b0460f25a87b1380f8e97a5959121 [3/7] ASoC: uniphier: add support for UniPhier AIO common driver
reproduce:
# apt-get install sparse
git checkout f37fe2f9987b0460f25a87b1380f8e97a5959121
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> sound/soc/uniphier/aio-core.c:907:5: sparse: symbol 'aiodma_rb_get_rp' was not declared. Should it be
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next reply other threads:[~2018-02-12 17:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 17:53 kbuild test robot [this message]
2018-02-12 17:53 ` [RFC PATCH asoc] ASoC: uniphier: aiodma_rb_get_rp() can be static kbuild test robot
2018-02-13 12:16 ` Applied "ASoC: uniphier: aiodma_rb_get_rp() can be static" to the asoc tree 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=201802130150.A223WMAh%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kbuild-all@01.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=suzuki.katsuhiro@socionext.com \
--cc=tiwai@suse.com \
--cc=yamada.masahiro@socionext.com \
/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