From: kernel test robot <lkp@intel.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [omap-audio:peter/linux-next-wip 11/42] sound/soc/soc-utils.c:251:34: warning: unused variable 'soc_dummy_ids'
Date: Tue, 26 Dec 2023 04:15:49 +0800 [thread overview]
Message-ID: <202312260449.JkrDDoWw-lkp@intel.com> (raw)
tree: https://github.com/omap-audio/linux-audio peter/linux-next-wip
head: b30de2d93893b64d7886860417b12948ec22be5a
commit: 5c1fa02438f03e25bddb0c82ff0b1fe4296cbdbc [11/42] ASoC: soc-utils: HACK: DT binding for snd-soc-dummy
config: i386-buildonly-randconfig-006-20231225 (https://download.01.org/0day-ci/archive/20231226/202312260449.JkrDDoWw-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231226/202312260449.JkrDDoWw-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/202312260449.JkrDDoWw-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> sound/soc/soc-utils.c:251:34: warning: unused variable 'soc_dummy_ids' [-Wunused-const-variable]
static const struct of_device_id soc_dummy_ids[] = {
^
1 warning generated.
vim +/soc_dummy_ids +251 sound/soc/soc-utils.c
250
> 251 static const struct of_device_id soc_dummy_ids[] = {
252 { .compatible = "linux,snd-soc-dummy", },
253 { }
254 };
255 MODULE_DEVICE_TABLE(of, soc_dummy_ids);
256
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-12-25 20:16 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=202312260449.JkrDDoWw-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peter.ujfalusi@ti.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 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.