[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <fdd24e93-efad-0132-e1ff-b7f5f87e8efc@linux.intel.com>
Date: Mon, 22 Jul 2019 10:19:53 -0500
From: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
To: Arnd Bergmann <arnd@...db.de>,
Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc: ALSA Development Mailing List <alsa-devel@...a-project.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Takashi Iwai <tiwai@...e.com>,
Liam Girdwood <liam.r.girdwood@...ux.intel.com>,
Mark Brown <broonie@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [alsa-devel] [PATCH] ASoC: SOF: use __u32 instead of uint32_t in
uapi headers
On 7/22/19 8:39 AM, Arnd Bergmann wrote:
> On Sun, Jul 21, 2019 at 4:25 PM Masahiro Yamada
> <yamada.masahiro@...ionext.com> wrote:
>>
>> struct snd_sof_blk_hdr {
>> enum snd_sof_fw_blk_type type;
>> - uint32_t size; /* bytes minus this header */
>> - uint32_t offset; /* offset from base */
>> + __u32 size; /* bytes minus this header */
>> + __u32 offset; /* offset from base */
>> } __packed;
>>
>
> On a related note: Using an 'enum' in an ABI structure is not portable
> across architectures. This is probably fine in a UAPI as long as user
> and kernel space agree on the size of an enum, but if the same
> structure is used to talk to the firmware, it won't work on architectures
> that have a different size for the first field.
yes, we've removed all enums in SOF and missed this one. This should be
changed, thanks for the note.
Powered by blists - more mailing lists