From: kernel test robot <lkp@intel.com>
To: Cezary Rojewski <cezary.rojewski@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, Mark Brown <broonie@kernel.org>
Subject: [broonie-ci:v2_20250123_cezary_rojewski_asoc_intel_avs_add_support_for_maliboulake_configuration 4/11] sound/soc/intel/avs/boards/pcm3168a.c:69:33: warning: 'avs_pcm3168a_ops' defined but not used
Date: Mon, 3 Feb 2025 13:58:06 +0800 [thread overview]
Message-ID: <202502031332.lVgdnyQV-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/ci.git v2_20250123_cezary_rojewski_asoc_intel_avs_add_support_for_maliboulake_configuration
head: 3318c70b5b94baa4e764ab05fa97c74643e7dc35
commit: b0d1438e2006a914d55496f4a5e588ca9d3c0a6f [4/11] ASoC: Intel: avs: Add pcm3168a machine board
config: s390-allyesconfig (https://download.01.org/0day-ci/archive/20250203/202502031332.lVgdnyQV-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250203/202502031332.lVgdnyQV-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202502031332.lVgdnyQV-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> sound/soc/intel/avs/boards/pcm3168a.c:69:33: warning: 'avs_pcm3168a_ops' defined but not used [-Wunused-const-variable=]
69 | static const struct snd_soc_ops avs_pcm3168a_ops = {
| ^~~~~~~~~~~~~~~~
vim +/avs_pcm3168a_ops +69 sound/soc/intel/avs/boards/pcm3168a.c
68
> 69 static const struct snd_soc_ops avs_pcm3168a_ops = {
70 .hw_params = avs_pcm3168a_hw_params,
71 };
72
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-03 5:58 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=202502031332.lVgdnyQV-lkp@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.