From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] ASoC: Ux500: Fix build error pertaining to missing include file
Date: Thu, 31 Jan 2013 20:37:48 +0800 [thread overview]
Message-ID: <20130131123744.GG11078@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1359635640-1932-1-git-send-email-lee.jones@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 275 bytes --]
On Thu, Jan 31, 2013 at 12:34:00PM +0000, Lee Jones wrote:
> Some compilers complain when building sound for MOP500:
>
> sound/soc/ux500/mop500.c:27:27:
> fatal error: mop500_ab8500.h: No such file or directory
Should be kernel version dependant I expect...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-01-31 12:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 12:34 [PATCH 1/1] ASoC: Ux500: Fix build error pertaining to missing include file Lee Jones
2013-01-31 12:37 ` Mark Brown [this message]
2013-01-31 13:03 ` Lee Jones
2013-01-31 13:06 ` Mark Brown
2013-01-31 14:07 ` Lee Jones
2013-01-31 14:10 ` Mark Brown
2013-01-31 14:21 ` Lee Jones
2013-01-31 14:33 ` Mark Brown
2013-01-31 14:47 ` Lee Jones
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=20130131123744.GG11078@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
/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