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-2026-03-27 82/106] sound/soc/intel/avs/pcm.c:1403:10: warning: variable 'ret' is uninitialized when used here
Date: Sat, 28 Mar 2026 00:00:00 +0800 [thread overview]
Message-ID: <202603272354.8LQSBKkh-lkp@intel.com> (raw)
tree: https://github.com/morimoto/linux sound-cleanup-2026-03-27
head: b547ff73a13ed8ce92e8e208ccd27884077b160b
commit: a22cf4c5c5139a4eb0afdd43d21ab0c8e359594b [82/106] ASoC: intel: avs: use snd_soc_component_alloc()
config: s390-allmodconfig (https://download.01.org/0day-ci/archive/20260327/202603272354.8LQSBKkh-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260327/202603272354.8LQSBKkh-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/202603272354.8LQSBKkh-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> sound/soc/intel/avs/pcm.c:1403:10: warning: variable 'ret' is uninitialized when used here [-Wuninitialized]
1403 | return ret;
| ^~~
sound/soc/intel/avs/pcm.c:1391:9: note: initialize the variable 'ret' to silence this warning
1391 | int ret;
| ^
| = 0
1 warning generated.
vim +/ret +1403 sound/soc/intel/avs/pcm.c
1384
1385 int avs_register_component(struct device *dev, const char *name,
1386 struct snd_soc_component_driver *drv,
1387 struct snd_soc_dai_driver *cpu_dais, int num_cpu_dais)
1388 {
1389 struct avs_soc_component *acomp;
1390 char *cpname;
1391 int ret;
1392
1393 cpname = devm_kstrdup(dev, name, GFP_KERNEL);
1394 if (!cpname)
1395 return -ENOMEM;
1396
1397 acomp = devm_kzalloc(dev, sizeof(*acomp), GFP_KERNEL);
1398 if (!acomp)
1399 return -ENOMEM;
1400
1401 acomp->base = snd_soc_component_alloc(dev, drv, NULL, cpname, NULL, NULL);
1402 if (!acomp->base)
> 1403 return ret;
1404
1405 snd_soc_component_attach_priv(acomp->base, acomp);
1406 INIT_LIST_HEAD(&acomp->node);
1407
1408 drv->use_dai_pcm_id = !obsolete_card_names;
1409
1410 return snd_soc_component_add(acomp->base, cpu_dais, num_cpu_dais);
1411 }
1412
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-27 16:00 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=202603272354.8LQSBKkh-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 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.