From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Vinod Koul <vinod.koul@linux.intel.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] ASoC: dapm: Fix x86_64 build warning.
Date: Mon, 23 Apr 2012 13:28:44 +0100 [thread overview]
Message-ID: <20120423122844.GN8318@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1335183754.31825.109.camel@vkoul-udesk3>
[-- Attachment #1.1: Type: text/plain, Size: 709 bytes --]
On Mon, Apr 23, 2012 at 05:52:34PM +0530, Vinod Koul wrote:
> On Mon, 2012-04-23 at 13:16 +0100, Mark Brown wrote:
> > On Mon, Apr 23, 2012 at 10:31:15AM +0100, Liam Girdwood wrote:
> > > Fixes the following build warning on x86_64.
> > Applied, thanks.
> Just wondering, do we have a x86-64 system running asoc?
We should do though we don't currently - see the recent discussion about
the ice drivers. There are some PC sound cards (mostly high end or old
ones, or tuner cards) which have a setup like ASoC where there's a CODEC
on an I2C bus and a "platform" which in this case is a PCI type device.
At a high level they look the same as embedded hardware with several
chips glued together in software.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2012-04-23 12:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 9:31 [PATCH] ASoC: dapm: Fix x86_64 build warning Liam Girdwood
2012-04-23 12:16 ` Mark Brown
2012-04-23 12:22 ` Vinod Koul
2012-04-23 12:28 ` Mark Brown [this message]
2012-04-23 15:34 ` Takashi Iwai
2012-04-23 16:10 ` 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=20120423122844.GN8318@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@ti.com \
--cc=vinod.koul@linux.intel.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 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).