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-cleanup-2025-03-07 40/40] sound/soc/soc-core.c:2895:80: error: use of undeclared identifier 'name'
Date: Mon, 10 Mar 2025 15:05:08 +0800 [thread overview]
Message-ID: <202503101524.cxor4d3p-lkp@intel.com> (raw)
tree: https://github.com/morimoto/linux sound-cleanup-2025-03-07
head: 609577579ecf4de9913d0d83a96d240bd935a4a1
commit: 609577579ecf4de9913d0d83a96d240bd935a4a1 [40/40] ASoC: soc-core: merge snd_soc_unregister_component() and snd_soc_unregister_component_by_driver()
config: x86_64-buildonly-randconfig-004-20250310 (https://download.01.org/0day-ci/archive/20250310/202503101524.cxor4d3p-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250310/202503101524.cxor4d3p-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/202503101524.cxor4d3p-lkp@intel.com/
All errors (new ones prefixed by >>):
>> sound/soc/soc-core.c:2895:80: error: use of undeclared identifier 'name'
2895 | struct snd_soc_component *component = snd_soc_lookup_component_nolocked(dev, name);
| ^
1 error generated.
vim +/name +2895 sound/soc/soc-core.c
2877
2878 /**
2879 * snd_soc_unregister_component_by_driver - Unregister component using a given driver
2880 * from the ASoC core
2881 *
2882 * @dev: The device to unregister
2883 * @component_driver: The component driver to unregister
2884 */
2885 void snd_soc_unregister_component_by_driver(struct device *dev,
2886 const struct snd_soc_component_driver *component_driver)
2887 {
2888 const char *driver_name = NULL;
2889
2890 if (component_driver)
2891 driver_name = component_driver->name;
2892
2893 mutex_lock(&client_mutex);
2894 while (1) {
> 2895 struct snd_soc_component *component = snd_soc_lookup_component_nolocked(dev, name);
2896
2897 if (!component)
2898 break;
2899
2900 snd_soc_del_component_unlocked(component);
2901 }
2902 mutex_unlock(&client_mutex);
2903 }
2904 EXPORT_SYMBOL_GPL(snd_soc_unregister_component_by_driver);
2905
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-03-10 7:06 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=202503101524.cxor4d3p-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