From: kernel test robot <[email protected]>
To: Takashi Iwai <[email protected]>
Cc: [email protected], Ammar Faizi <[email protected]>,
GNU/Weeb Mailing List <[email protected]>,
[email protected]
Subject: [ammarfaizi2-block:tiwai/sound/master 42/45] sound/pci/hda/patch_sigmatel.c:4450:31: warning: unused variable 'spec'
Date: Mon, 5 Sep 2022 17:55:58 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
tree: https://github.com/ammarfaizi2/linux-block tiwai/sound/master
head: a6c91e26b44722382fb45d782d25d9ed77bbb184
commit: 414d38ba871092aeac4ed097ac4ced89486646f7 [42/45] ALSA: hda/sigmatel: Keep power up while beep is enabled
config: x86_64-randconfig-a004-20220905 (https://download.01.org/0day-ci/archive/20220905/[email protected]/config)
compiler: gcc-11 (Debian 11.3.0-5) 11.3.0
reproduce (this is a W=1 build):
# https://github.com/ammarfaizi2/linux-block/commit/414d38ba871092aeac4ed097ac4ced89486646f7
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block tiwai/sound/master
git checkout 414d38ba871092aeac4ed097ac4ced89486646f7
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash sound/pci/hda/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <[email protected]>
All warnings (new ones prefixed by >>):
sound/pci/hda/patch_sigmatel.c: In function 'stac_check_power_status':
>> sound/pci/hda/patch_sigmatel.c:4450:31: warning: unused variable 'spec' [-Wunused-variable]
4450 | struct sigmatel_spec *spec = codec->spec;
| ^~~~
vim +/spec +4450 sound/pci/hda/patch_sigmatel.c
4447
4448 static int stac_check_power_status(struct hda_codec *codec, hda_nid_t nid)
4449 {
> 4450 struct sigmatel_spec *spec = codec->spec;
4451 int ret = snd_hda_gen_check_power_status(codec, nid);
4452
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-09-05 9:56 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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