From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Anand Gadiyar <gadiyar@ti.com>
Cc: linux-omap@vger.kernel.org, alsa-devel@alsa-project.org,
Tony Lindgren <tony@atomide.com>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] omap: zoom2: fix build break due to ASoC changes
Date: Fri, 1 Oct 2010 13:36:05 -0700 [thread overview]
Message-ID: <20101001203605.GE21157@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1285965011-17384-1-git-send-email-gadiyar@ti.com>
On Sat, Oct 02, 2010 at 02:00:11AM +0530, Anand Gadiyar wrote:
> Commit f0fba2ad1b6 (ASoC: multi-component - ASoC
> Multi-Component Support) in linux-next as of 20101001
> broke omap builds with the following errors.
Acked-by: Mark Brown <brooonie@opensource.wolfsonmicro.com>
since it fixes build breakage but it looks like it'll result in reduced
functionality so a nicer fix would be good.
next prev parent reply other threads:[~2010-10-01 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 20:30 [PATCH] omap: zoom2: fix build break due to ASoC changes Anand Gadiyar
2010-10-01 20:36 ` Mark Brown [this message]
2010-10-01 20:43 ` Anand Gadiyar
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=20101001203605.GE21157@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=gadiyar@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=tony@atomide.com \
/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.