From: Takashi Iwai <tiwai@suse.de>
To: mengdong.lin@linux.intel.com
Cc: alsa-devel@alsa-project.org, vinod.koul@intel.com,
mengdong.lin@intel.com, broonie@kernel.org,
liam.r.girdwood@intel.com, subhransu.s.prusty@intel.com
Subject: Re: [PATCH] topology: Include <linux/types.h> in API header file
Date: Fri, 06 Nov 2015 13:59:41 +0100 [thread overview]
Message-ID: <s5hoaf7z3k2.wl-tiwai@suse.de> (raw)
In-Reply-To: <1446813576-29295-1-git-send-email-mengdong.lin@linux.intel.com>
On Fri, 06 Nov 2015 13:39:36 +0100,
mengdong.lin@linux.intel.com wrote:
>
> From: Mengdong Lin <mengdong.lin@linux.intel.com>
>
> Include <linux/types.h> in the API header file topology.h
>
> The struct snd_tplg_stream_caps_template has a member "formats"
> of type __le64. So <linux/types.h> is needed.
We shouldn't use __le64 for user-space API. I couldn't find it in
include/topology.h. Where is it used?
Of course, it's fine to use it for kernel ABI. But then linux/types.h
is already included in local.h, so it shouldn't be a problem.
Takashi
>
> Signed-off-by: Mengdong Lin <mengdong.lin@linux.intel.com>
>
> diff --git a/include/topology.h b/include/topology.h
> index b631871..5ee67e2 100644
> --- a/include/topology.h
> +++ b/include/topology.h
> @@ -21,6 +21,8 @@
> #ifndef __ALSA_TOPOLOGY_H
> #define __ALSA_TOPOLOGY_H
>
> +#include <linux/types.h>
> +
> #ifdef __cplusplus
> extern "C" {
> #endif
> --
> 1.9.1
>
next prev parent reply other threads:[~2015-11-06 12:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 12:39 [PATCH] topology: Include <linux/types.h> in API header file mengdong.lin
2015-11-06 12:59 ` Takashi Iwai [this message]
2015-11-06 13:31 ` Vinod Koul
2015-11-06 13:33 ` Takashi Iwai
2015-11-06 14:37 ` Liam Girdwood
2015-11-06 14:40 ` Takashi Iwai
2015-11-06 14:57 ` Liam Girdwood
2015-11-09 14:04 ` Subhransu S. Prusty
2015-11-10 12:29 ` Vinod Koul
2015-11-10 12:29 ` Jaroslav Kysela
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=s5hoaf7z3k2.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@intel.com \
--cc=mengdong.lin@intel.com \
--cc=mengdong.lin@linux.intel.com \
--cc=subhransu.s.prusty@intel.com \
--cc=vinod.koul@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