linux-kernel - Re: [PATCH] ASoC: SOF: ipc: replace "enum sof_comp_type" field with "uint32

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <172471182590.865478.17639735740855065708.b4-ty@kernel.org>
Date: Mon, 26 Aug 2024 23:37:05 +0100
From: Mark Brown <broonie@...nel.org>
To: Jaroslav Kysela <perex@...ex.cz>, Liam Girdwood <lgirdwood@...il.com>, 
 Takashi Iwai <tiwai@...e.com>, 
 Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>, 
 Bard Liao <yung-chuan.liao@...ux.intel.com>, 
 Laurentiu Mihalcea <laurentiumihalcea111@...il.com>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: SOF: ipc: replace "enum sof_comp_type" field
 with "uint32_t"

On Mon, 26 Aug 2024 14:24:42 -0400, Laurentiu Mihalcea wrote:
> Normally, the type of enums is "unsigned int" or "int". GCC has
> the "-fshort-enums" option, which instructs the compiler to
> use the smallest data type that can hold all the values in
> the enum (i.e: char, short, int or their unsigned variants).
> 
> According to the GCC documentation, "-fshort-enums" may be
> default on some targets. This seems to be the case for SOF
> when built for a certain 32-bit ARM platform.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/1] ASoC: SOF: ipc: replace "enum sof_comp_type" field with "uint32_t"
      commit: 22652022c7eef3c4ad6ab5f13a6dfc7f25f853d4

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark