Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: kbuild test robot <lkp@intel.com>
Cc: alsa-devel@alsa-project.org,
	"Dharageswari.R" <dharageswari.r@intel.com>,
	tiwai@suse.de, Jayachandran B <jayachandran.b@intel.com>,
	liam.r.girdwood@linux.intel.com, patches.audio@intel.com,
	broonie@kernel.org, kbuild-all@01.org
Subject: Re: [PATCH v2 08/13] ASoC: Intel: Skylake: Use CGCTL.MISCBDCGE for Phrase detection notification
Date: Mon, 14 Dec 2015 09:52:42 +0530	[thread overview]
Message-ID: <20151214042242.GI1854@localhost> (raw)
In-Reply-To: <201512130213.fd9SElQX%fengguang.wu@intel.com>

On Sun, Dec 13, 2015 at 02:46:08AM +0800, kbuild test robot wrote:
> Hi Dharageswari.R,
> 
> [auto build test ERROR on asoc/for-next]
> [also build test ERROR on next-20151211]
> [cannot apply to v4.4-rc4]
> 
> url:    https://github.com/0day-ci/linux/commits/Vinod-Koul/ASoC-Intel-Skylake-Update-to-SKL-driver/20151212-201340
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
> config: i386-allmodconfig (attached as .config)
> reproduce:
>         # save the attached .config to linux build tree
>         make ARCH=i386 
> 
> All errors (new ones prefixed by >>):
> 
> >> ERROR: "skl_enable_miscbdcge" undefined!

I will update this one, thanks for reporting

-- 
~Vinod

  parent reply	other threads:[~2015-12-14  4:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-12 12:06 [PATCH v2 00/13] ASoC: Intel: Skylake: Update to SKL driver Vinod Koul
2015-12-12 12:06 ` [PATCH v2 01/13] ASoC: Intel: Skylake: Clear stream registers before stream setup Vinod Koul
2015-12-12 12:06 ` [PATCH v2 02/13] ASoC: Intel: Skylake: Fix to set pipe state to invalid when deleting Vinod Koul
2015-12-12 12:06 ` [PATCH v2 03/13] ALSA: hdac: Add support for hda DMA Resume capability Vinod Koul
2015-12-12 12:06 ` [PATCH v2 04/13] ALSA: hdac: couple the hda DMA stream in cleanup Vinod Koul
2015-12-12 12:06 ` [PATCH v2 05/13] ALSA: hdac: Increase timeout value for link power check Vinod Koul
2015-12-12 12:06 ` [PATCH v2 06/13] ALSA: hdac: add snd_hdac_ext_bus_link_power_up_all Vinod Koul
2015-12-12 12:06 ` [PATCH v2 07/13] ASoC: Intel: Skylake: fix reset controller sequencing Vinod Koul
2015-12-12 12:06 ` [PATCH v2 08/13] ASoC: Intel: Skylake: Use CGCTL.MISCBDCGE for Phrase detection notification Vinod Koul
     [not found]   ` <201512130213.fd9SElQX%fengguang.wu@intel.com>
2015-12-14  4:22     ` Vinod Koul [this message]
2015-12-12 12:06 ` [PATCH v2 09/13] ASoC: Intel: Skylake: manage link power in active suspend Vinod Koul
2015-12-12 12:06 ` [PATCH v2 10/13] ASoC: Intel: Skylake: enable interrupt as wake source " Vinod Koul
2015-12-12 12:06 ` [PATCH v2 11/13] ASoC: Intel: Skylake: Add DMA resume position in Trigger resume/suspend Vinod Koul
2015-12-12 12:06 ` [PATCH v2 12/13] ASoC: Intel: Skylake: Reconfigure Link stream on suspend/resume Vinod Koul
2015-12-12 12:06 ` [PATCH v2 13/13] ASoC: Intel: Skylake: Add Resume capability in PCM info Vinod Koul

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=20151214042242.GI1854@localhost \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=dharageswari.r@intel.com \
    --cc=jayachandran.b@intel.com \
    --cc=kbuild-all@01.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=lkp@intel.com \
    --cc=patches.audio@intel.com \
    --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