From: Liam Girdwood <lrg@ti.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH 1/4] ASoC: firmware: Add support for FW based kcontrols.
Date: Thu, 29 Nov 2012 16:01:25 +0000 [thread overview]
Message-ID: <50B786D5.1010003@ti.com> (raw)
In-Reply-To: <50B78498.40406@ti.com>
On 29/11/12 15:51, Liam Girdwood wrote:
> On 29/11/12 15:15, Takashi Iwai wrote:
>> At Thu, 29 Nov 2012 12:08:18 +0000,
>> Liam Girdwood wrote:
>>>
>>> On 19/11/12 18:36, Takashi Iwai wrote:
>
>>>>
>>>> For the sound stuff, the patch is queued for 3.8 in for-next branch.
>>>> Please rebase on it.
>>>
>>> Done, but I'm now seeing some type conflict errors when building my userspace
>>> tools (i.e. after moving to include uapi/sound/asound.h from sound/asound.h).
>>>
>>> e.g.
>>>
>>> #include <stdlib.h>
>>> #include <uapi/sound/asound.h>
>>>
>>> int main ()
>>> {
>>> }
>>>
>>> gives :-
>>>
>>> gcc uapi-test.c -I ~/source/linux.git/include
>>
>> Pass -I ~/source/linux.git/include/uapi
>>
>> then
>>
>> #include <sound/asound.h>
>>
>
> Ah, I did initially try this before emailing :-
>
> gcc uapi-test.c -I ~/source/linux.git/include/uapi
> In file included from
> /home/lrg/source/linux.git/include/uapi/sound/asound.h:26:0,
> from uapi-test.c:2:
> /home/lrg/source/linux.git/include/uapi/linux/types.h:9:2: warning: #warning
> "Attempt to use kernel headers from user space, see
> http://kernelnewbies.org/KernelHeaders" [-Wcpp]
> In file included from
> /home/lrg/source/linux.git/include/uapi/linux/posix_types.h:4:0,
> from /home/lrg/source/linux.git/include/uapi/linux/types.h:13,
> from /home/lrg/source/linux.git/include/uapi/sound/asound.h:26,
> from uapi-test.c:2:
> /home/lrg/source/linux.git/include/uapi/linux/stddef.h:1:28: fatal error:
> linux/compiler.h: No such file or directory
>
> adding -D__EXPORTED_HEADERS__ to gcc command line gets rid of the warning, but
> it seems we are missing compiler.h (even in todays linux-next).
>
> If this works for you, it may be an issue at my end.
>
In fact adding the old include path at the end works, but is probably an
interim fix until the uapi work is completed.
gcc uapi-test.c -I ~/source/linux.git/include/uapi -D__EXPORTED_HEADERS__ -I
/home/lrg/source/linux.git/include/
Thanks
Liam
next prev parent reply other threads:[~2012-11-29 16:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 18:12 [PATCH 1/4] ASoC: firmware: Add support for FW based kcontrols Liam Girdwood
2012-11-19 18:12 ` [PATCH 2/4] ASoC: firmware: Add support for FW based widgets Liam Girdwood
2012-11-20 2:16 ` Mark Brown
2012-11-19 18:12 ` [PATCH 3/4] ASoC: firmware core: Add core support for dynamic kcontrols and widgets Liam Girdwood
2012-11-20 2:36 ` Mark Brown
2012-11-20 12:19 ` Liam Girdwood
2012-11-19 18:12 ` [PATCH 4/4] ASoC: firmware core: Add core support to create and destroy firmware components Liam Girdwood
2012-11-19 18:46 ` Takashi Iwai
2012-11-20 12:03 ` Liam Girdwood
2012-11-20 12:05 ` Takashi Iwai
2012-11-21 0:30 ` Mark Brown
2012-11-21 6:43 ` Takashi Iwai
2012-11-21 6:49 ` Mark Brown
2012-11-20 3:27 ` Mark Brown
2012-11-20 15:14 ` Liam Girdwood
2012-11-21 0:43 ` Mark Brown
2012-11-21 10:21 ` Liam Girdwood
2012-11-21 10:37 ` Mark Brown
2012-11-21 11:16 ` Liam Girdwood
2012-11-21 11:52 ` Mark Brown
2012-11-19 18:36 ` [PATCH 1/4] ASoC: firmware: Add support for FW based kcontrols Takashi Iwai
2012-11-29 12:08 ` Liam Girdwood
2012-11-29 15:15 ` Takashi Iwai
2012-11-29 15:51 ` Liam Girdwood
2012-11-29 16:01 ` Liam Girdwood [this message]
2012-11-29 17:35 ` Takashi Iwai
2012-11-29 17:39 ` Liam Girdwood
2012-11-20 2:11 ` 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=50B786D5.1010003@ti.com \
--to=lrg@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=tiwai@suse.de \
/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.