From: Takashi Iwai <tiwai@suse•de>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Hui Wang <hui.wang@canonical•com>
Subject: Re: linux-next: build warning after merge of the sound-current tree
Date: Wed, 12 Aug 2020 09:03:23 +0200 [thread overview]
Message-ID: <s5hk0y4z6pw.wl-tiwai@suse.de> (raw)
In-Reply-To: <20200812092119.710d92ec@canb.auug.org.au>
On Wed, 12 Aug 2020 01:21:19 +0200,
Stephen Rothwell wrote:
>
> Hi all,
>
> After merging the sound-current tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> sound/pci/hda/patch_realtek.c: In function 'alc285_fixup_hp_gpio_led':
> sound/pci/hda/patch_realtek.c:4163:19: warning: unused variable 'spec' [-Wunused-variable]
> 4163 | struct alc_spec *spec = codec->spec;
> | ^~~~
>
> Introduced by commit
>
> 404690649e6a ("ALSA: hda - reverse the setting value in the micmute_led_set")
Thanks, fixed now in sound git tree.
Takashi
prev parent reply other threads:[~2020-08-12 7:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 23:21 linux-next: build warning after merge of the sound-current tree Stephen Rothwell
2020-08-12 7:03 ` Takashi Iwai [this message]
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=s5hk0y4z6pw.wl-tiwai@suse.de \
--to=tiwai@suse$(echo .)de \
--cc=hui.wang@canonical$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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