Linux-Next discussions
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warning after merge of the final tree (sound tree related)
Date: Thu, 16 Sep 2010 07:46:38 +0200	[thread overview]
Message-ID: <s5h1v8ujl4x.wl%tiwai@suse.de> (raw)
In-Reply-To: <20100916150948.cc9ebed8.sfr@canb.auug.org.au>

At Thu, 16 Sep 2010 15:09:48 +1000,
Stephen Rothwell wrote:
> 
> [1  <text/plain; US-ASCII (quoted-printable)>]
> Hi Takashi,
> 
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) produced this warning:
> 
> sound/pci/hda/patch_conexant.c: In function 'cx_auto_parse_beep':
> sound/pci/hda/patch_conexant.c:3565: warning: unused variable 'spec'
> 
> Introduced by commit 05f7349fc754f20cf92009934498d92435518141 ("ALSA: hda
> - Preliminary support for new Conexant audio codecs").

Thanks, fixed now.


Takashi

      parent reply	other threads:[~2010-09-16  5:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-16  5:09 linux-next: build warning after merge of the final tree (sound tree related) Stephen Rothwell
2010-09-16  5:10 ` Stephen Rothwell
2010-09-16  5:46 ` 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=s5h1v8ujl4x.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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