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-04-22 82/103] sound/soc/soc-dapm.c:981: warning: Function parameter or struct member 'dapm' not described in 'snd_soc_dapm_init_bias_level'
Date: Tue, 22 Apr 2025 21:44:27 +0800 [thread overview]
Message-ID: <202504222110.BJ3jQ3V8-lkp@intel.com> (raw)
tree: https://github.com/morimoto/linux sound-cleanup-2025-04-22
head: f743db58ae26ad957c2beb5f627c328ec8473d30
commit: b0b8854846877361dd5c29f44ce035743fbd471d [82/103] ASoC: soc-dapm: tidyup snd_soc_dapm_init_bias_level()
config: i386-buildonly-randconfig-002-20250422 (https://download.01.org/0day-ci/archive/20250422/202504222110.BJ3jQ3V8-lkp@intel.com/config)
compiler: clang version 20.1.2 (https://github.com/llvm/llvm-project 58df0ef89dd64126512e4ee27b4ac3fd8ddf6247)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250422/202504222110.BJ3jQ3V8-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/202504222110.BJ3jQ3V8-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> sound/soc/soc-dapm.c:981: warning: Function parameter or struct member 'dapm' not described in 'snd_soc_dapm_init_bias_level'
>> sound/soc/soc-dapm.c:981: warning: Excess function parameter 'component' description in 'snd_soc_dapm_init_bias_level'
vim +981 sound/soc/soc-dapm.c
966
967 /**
968 * snd_soc_dapm_init_bias_level() - Initialize DAPM bias level
969 * @component: The DAPM context to initialize
970 * @level: The DAPM level to initialize to
971 *
972 * This function only sets the driver internal state of the DAPM level and will
973 * not modify the state of the device. Hence it should not be used during normal
974 * operation, but only to synchronize the internal state to the device state.
975 * E.g. during driver probe to set the DAPM level to the one corresponding with
976 * the power-on reset state of the device.
977 *
978 * To change the DAPM state of the device use snd_soc_dapm_set_bias_level().
979 */
980 void snd_soc_dapm_init_bias_level(struct snd_soc_dapm_context *dapm, enum snd_soc_bias_level level)
> 981 {
982 dapm->bias_level = level;
983 }
984 EXPORT_SYMBOL_GPL(snd_soc_dapm_init_bias_level);
985
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-04-22 13:44 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=202504222110.BJ3jQ3V8-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