From: Lee Jones <lee.jones@linaro.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
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 14:07:35 +0000 [thread overview]
Message-ID: <20130131140735.GD2042@gmail.com> (raw)
In-Reply-To: <20130131130631.GA12824@opensource.wolfsonmicro.com>
On Thu, 31 Jan 2013, Mark Brown wrote:
> On Thu, Jan 31, 2013 at 01:03:40PM +0000, Lee Jones wrote:
> > On Thu, 31 Jan 2013, Mark Brown wrote:
> > > 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...
>
> > What do you mean?
>
> I'm a bit surprised the compiler would change something like that, I'd
> expect it to be more the build system.
You've lost me.
When I compile this file it succeeds. When the person who reported
this bug compiles, it fails with the error above.
mop500_ab8500.h is actually in the same directory as the file
including it, so it should by rights be encapsulated in "" and not <>,
right?
--
Lee Jones
Linaro ST-Ericsson Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2013-01-31 14:07 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
2013-01-31 13:03 ` Lee Jones
2013-01-31 13:06 ` Mark Brown
2013-01-31 14:07 ` Lee Jones [this message]
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=20130131140735.GD2042@gmail.com \
--to=lee.jones@linaro.org \
--cc=broonie@opensource.wolfsonmicro.com \
--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