alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	kernel-janitors@vger.kernel.org
Subject: Re: sound/pci/hda/hda_codec.c:1435:46: error: 'AC_VERB_GET_CON' undeclared
Date: Sun, 14 Oct 2012 10:39:53 +0800	[thread overview]
Message-ID: <20121014023953.GA8713@localhost> (raw)
In-Reply-To: <s5h7gquixlv.wl%tiwai@suse.de>

On Sat, Oct 13, 2012 at 10:29:16AM +0200, Takashi Iwai wrote:
> At Sat, 13 Oct 2012 01:01:09 +0800,
> Fengguang Wu wrote:
> > 
> > Hi Takashi,
> > 
> > FYI, kernel build failed on
> > 
> > commit: 645cf3b5656e47fa9a46e2fbc8d212ab572ab05b  Merge branch 'topic/3.8'
> > config: x86_64-allyesdebian (attached as .config)
> > 
> > 
> > All error/warnings:
> > 
> > sound/pci/hda/hda_codec.c: In function 'update_pcm_stream_id':
> > sound/pci/hda/hda_codec.c:1435:46: error: 'AC_VERB_GET_CON' undeclared (first use in this function)
> > sound/pci/hda/hda_codec.c:1435:46: note: each undeclared identifier is reported only once for each function it appears in
> 
> Thanks, this must be already fixed.  It was a temporary merge error.
> (One shouldn't work during updating the system....)

OK. Takashi, Mark, the build system can now avoid testing selected
trees during the merge window. Shall I add your trees to the list?

Thanks,
Fengguang

  reply	other threads:[~2012-10-14  2:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20121012170109.GD20312@localhost>
2012-10-13  8:29 ` sound/pci/hda/hda_codec.c:1435:46: error: 'AC_VERB_GET_CON' undeclared Takashi Iwai
2012-10-14  2:39   ` Fengguang Wu [this message]
2012-10-14  7:44     ` Takashi Iwai
2012-10-15  0:59     ` Mark Brown
2012-10-15  1:49       ` Fengguang Wu

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=20121014023953.GA8713@localhost \
    --to=fengguang.wu@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=tiwai@suse.de \
    /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;
as well as URLs for NNTP newsgroup(s).