From: kbuild test robot <fengguang.wu@intel.com>
To: "oder_chiou@realtek.com" <oder_chiou@realtek.com>
Cc: kbuild-all@01.org, alsa-devel@alsa-project.org,
Mark Brown <broonie@kernel.org>, Bard Liao <bardliao@realtek.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
linux-kernel@vger.kernel.org
Subject: [asoc:topic/rt5659 1/3] sound/soc/codecs/rt5659.c:4048:6: sparse: symbol 'rt5659_intel_hd_header_probe_setup' was not declared. Should it be static?
Date: Tue, 13 Feb 2018 01:16:06 +0800 [thread overview]
Message-ID: <201802130145.hD2DgN3c%fengguang.wu@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git topic/rt5659
head: de86a33253d07675abbb1fa294ffb4f3df6f219e
commit: 041e74b71491acadad74b275e8b05add165d92b4 [1/3] ASoC: rt5659: Add the support of Intel HDA Header
reproduce:
# apt-get install sparse
git checkout 041e74b71491acadad74b275e8b05add165d92b4
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> sound/soc/codecs/rt5659.c:4048:6: sparse: symbol 'rt5659_intel_hd_header_probe_setup' 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:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 17:16 kbuild test robot [this message]
2018-02-12 17:16 ` [RFC PATCH asoc] ASoC: rt5659: rt5659_intel_hd_header_probe_setup() can be static kbuild test robot
2018-02-13 12:15 ` Applied "ASoC: rt5659: rt5659_intel_hd_header_probe_setup() 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=201802130145.hD2DgN3c%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=broonie@kernel.org \
--cc=kbuild-all@01.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oder_chiou@realtek.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.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
all inboxes | Powered by JetHome®