From: kernel test robot <lkp@intel.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [morimoto:sound-mod-2026-11-06-2 348/348] sound/soc/soc-pcm-mod.c:89:19: error: use of undeclared identifier 'soc_pcm_open'
Date: Sat, 14 Nov 2026 01:21:34 +0800 [thread overview]
Message-ID: <202611140104.oIJ6MIS5-lkp@intel.com> (raw)
tree: https://github.com/morimoto/linux sound-mod-2026-11-06-2
head: 9667cbd3f622480983c9c69e0525b2ca47c07f74
commit: 7454144fb3be295810104db73497ffa2d04a6254 [348/348] hoge
config: s390-allmodconfig (https://download.01.org/0day-ci/archive/20261114/202611140104.oIJ6MIS5-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 1b1fed44d3dcca649a9877915d57c3357a98124e)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261114/202611140104.oIJ6MIS5-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/202611140104.oIJ6MIS5-lkp@intel.com/
All errors (new ones prefixed by >>):
>> sound/soc/soc-pcm-mod.c:89:19: error: use of undeclared identifier 'soc_pcm_open'
89 | rtd->ops.open = soc_pcm_open;
| ^~~~~~~~~~~~
>> sound/soc/soc-pcm-mod.c:90:23: error: use of undeclared identifier 'soc_pcm_hw_params'
90 | rtd->ops.hw_params = soc_pcm_hw_params;
| ^~~~~~~~~~~~~~~~~
>> sound/soc/soc-pcm-mod.c:91:21: error: use of undeclared identifier 'soc_pcm_prepare'
91 | rtd->ops.prepare = soc_pcm_prepare;
| ^~~~~~~~~~~~~~~
>> sound/soc/soc-pcm-mod.c:92:21: error: use of undeclared identifier 'soc_pcm_trigger'
92 | rtd->ops.trigger = soc_pcm_trigger;
| ^~~~~~~~~~~~~~~
>> sound/soc/soc-pcm-mod.c:93:21: error: use of undeclared identifier 'soc_pcm_hw_free'
93 | rtd->ops.hw_free = soc_pcm_hw_free;
| ^~~~~~~~~~~~~~~
>> sound/soc/soc-pcm-mod.c:94:20: error: use of undeclared identifier 'soc_pcm_close'
94 | rtd->ops.close = soc_pcm_close;
| ^~~~~~~~~~~~~
>> sound/soc/soc-pcm-mod.c:95:21: error: use of undeclared identifier 'soc_pcm_pointer'
95 | rtd->ops.pointer = soc_pcm_pointer;
| ^~~~~~~~~~~~~~~
7 errors generated.
vim +/soc_pcm_open +89 sound/soc/soc-pcm-mod.c
68
69 /* create a new pcm */
70 int soc_new_pcm_mod(struct snd_soc_pcm_runtime *rtd)
71 {
72 // struct snd_soc_component *component;
73 struct snd_pcm *pcm;
74 int ret = 0, playback = 0, capture = 0;
75
76 ret = soc_get_playback_capture(rtd, &playback, &capture);
77 if (ret < 0)
78 goto err;
79
80 ret = soc_create_pcm(&pcm, rtd, playback, capture);
81 if (ret < 0)
82 goto err;
83
84 rtd->pcm = pcm;
85 pcm->nonatomic = rtd->dai_link->nonatomic;
86 pcm->private_data = rtd;
87 pcm->no_device_suspend = true;
88
> 89 rtd->ops.open = soc_pcm_open;
> 90 rtd->ops.hw_params = soc_pcm_hw_params;
> 91 rtd->ops.prepare = soc_pcm_prepare;
> 92 rtd->ops.trigger = soc_pcm_trigger;
> 93 rtd->ops.hw_free = soc_pcm_hw_free;
> 94 rtd->ops.close = soc_pcm_close;
> 95 rtd->ops.pointer = soc_pcm_pointer;
96
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-11-13 17:22 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=202611140104.oIJ6MIS5-lkp@intel.com \
--to=lkp@intel.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=llvm@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox