All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Jarkko Nikula <jhnikula@gmail.com>
Cc: linux-next@vger.kernel.org,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	alsa-devel@alsa-project.org,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: Fix build failure in soc-core.c
Date: Wed, 01 Dec 2010 09:50:48 +0000	[thread overview]
Message-ID: <1291197048.3292.2.camel@odin> (raw)
In-Reply-To: <1291187447-1247-1-git-send-email-jhnikula@gmail.com>

On Wed, 2010-12-01 at 09:10 +0200, Jarkko Nikula wrote:
> Commit 2eea392 "ASoC: Add support for optional auxiliary dailess codecs"
> causes a build failure in soc-core.c: soc_probe_aux_dev since code tries to
> access non-existing struct snd_soc_dapm_context and struct snd_soc_card
> members.
> 
> Root cause for this was a double accident. Author sent the RFC patch from
> top of another patch set and the RFC got committed. Fix the build failure
> by removing the code line that depends on that another patch set.
> 
> Signed-off-by: Jarkko Nikula <jhnikula@gmail.com>
> ---

Acked-by: Liam Girdwood <lrg@slimlogic.co.uk>
-- 
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk

WARNING: multiple messages have this Message-ID (diff)
From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Jarkko Nikula <jhnikula@gmail.com>
Cc: alsa-devel@alsa-project.org,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: [alsa-devel] [PATCH] ASoC: Fix build failure in soc-core.c
Date: Wed, 01 Dec 2010 09:50:48 +0000	[thread overview]
Message-ID: <1291197048.3292.2.camel@odin> (raw)
In-Reply-To: <1291187447-1247-1-git-send-email-jhnikula@gmail.com>

On Wed, 2010-12-01 at 09:10 +0200, Jarkko Nikula wrote:
> Commit 2eea392 "ASoC: Add support for optional auxiliary dailess codecs"
> causes a build failure in soc-core.c: soc_probe_aux_dev since code tries to
> access non-existing struct snd_soc_dapm_context and struct snd_soc_card
> members.
> 
> Root cause for this was a double accident. Author sent the RFC patch from
> top of another patch set and the RFC got committed. Fix the build failure
> by removing the code line that depends on that another patch set.
> 
> Signed-off-by: Jarkko Nikula <jhnikula@gmail.com>
> ---

Acked-by: Liam Girdwood <lrg@slimlogic.co.uk>
-- 
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk


  reply	other threads:[~2010-12-01  9:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01  0:31 linux-next: build failure after merge of the sound-asoc tree Stephen Rothwell
2010-12-01  7:10 ` [PATCH] ASoC: Fix build failure in soc-core.c Jarkko Nikula
2010-12-01  9:50   ` Liam Girdwood [this message]
2010-12-01  9:50     ` [alsa-devel] " Liam Girdwood
2010-12-01 11:36   ` Mark Brown

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=1291197048.3292.2.camel@odin \
    --to=lrg@slimlogic.co.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=jhnikula@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.