LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
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>,
	Kai-Heng Feng <kai.heng.feng@canonical.com>
Subject: Re: linux-next: build warning after merge of the sound tree
Date: Fri, 01 May 2020 09:33:17 +0200	[thread overview]
Message-ID: <s5hpnbohzya.wl-tiwai@suse.de> (raw)
In-Reply-To: <20200501140323.0e0f4a9d@canb.auug.org.au>

On Fri, 01 May 2020 06:03:23 +0200,
Stephen Rothwell wrote:
> 
> Hi all,
> 
> After merging the sound tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
> 
> sound/pci/hda/patch_realtek.c: In function 'alc_fixup_hp_gpio_led':
> sound/pci/hda/patch_realtek.c:4134:6: warning: unused variable 'err' [-Wunused-variable]
>  4134 |  int err;
>       |      ^~~
> 
> Introduced by commit
> 
>   87dc36482cab ("ALSA: hda/realtek - Add LED class support for micmute LED")

I submitted the fix patch now and it will be included later:
  https://lore.kernel.org/r/20200501072857.13720-1-tiwai@suse.de


thanks,

Takashi

  reply	other threads:[~2020-05-01  7:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-01  4:03 Stephen Rothwell
2020-05-01  7:33 ` Takashi Iwai [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-02-08 23:48 Stephen Rothwell
2023-02-09  3:14 ` Stephen Rothwell
2021-08-23 10:00 Stephen Rothwell
2021-08-23 14:27 ` Takashi Iwai
2019-12-12  0:28 Stephen Rothwell
2019-01-21  0:21 Stephen Rothwell
2019-01-21  8:13 ` Takashi Iwai
2010-03-30  3:48 Stephen Rothwell
2010-03-30  6:07 ` Takashi Iwai
2010-02-23  5:07 Stephen Rothwell
2010-02-23  5:20 ` Luke Yelavich
2010-02-23  7:11   ` Takashi Iwai

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=s5hpnbohzya.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=kai.heng.feng@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --subject='Re: linux-next: build warning after merge of the sound tree' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).