From: kbuild test robot <fengguang.wu@intel.com>
To: Rongjun Ying <rongjun.ying@csr.com>
Cc: kbuild-all@01.org, Barry Song <Barry.Song@csr.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [baohua:sirf-3.18 2573/2782] sound/soc/sirf/atlas7-iacc.c:168:24: sparse: symbol 'atlas7_iacc_dai_ops' was not declared. Should it be static?
Date: Fri, 6 Feb 2015 01:03:52 +0800 [thread overview]
Message-ID: <201502060130.hszyNa1F%fengguang.wu@intel.com> (raw)
tree: git://git.kernel.org/pub/scm/linux/kernel/git/baohua/linux sirf-3.18
head: d61ca44a1d96f134d35d31522ca8efb19a6e1451
commit: 81aba96393135459ac811ce78fe8f91a8b767b82 [2573/2782] ASoC: sirf: atlas7: Add internal audio codec controller driver
reproduce:
# apt-get install sparse
git checkout 81aba96393135459ac811ce78fe8f91a8b767b82
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> sound/soc/sirf/atlas7-iacc.c:168:24: sparse: symbol 'atlas7_iacc_dai_ops' was not declared. Should it be static?
sound/soc/sirf/atlas7-iacc.c:482:27: sparse: incorrect type in initializer (incompatible argument 4 (different address spaces))
sound/soc/sirf/atlas7-iacc.c:482:27: expected int ( *copy )( ... )
sound/soc/sirf/atlas7-iacc.c:482:27: got int ( static [toplevel] *<noident> )( ... )
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
http://lists.01.org/mailman/listinfo/kbuild Intel Corporation
next reply other threads:[~2015-02-05 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 17:03 kbuild test robot [this message]
2015-02-05 17:03 ` [PATCH baohua] ASoC: sirf: atlas7: atlas7_iacc_dai_ops can be static kbuild test robot
2015-02-05 17:11 ` Mark Brown
2015-02-06 2:35 ` [alsa-devel] " Barry Song
2015-03-10 3:41 ` Fengguang Wu
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=201502060130.hszyNa1F%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=Barry.Song@csr.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=rongjun.ying@csr.com \
--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;
as well as URLs for NNTP newsgroup(s).