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
| ||
|
Message-Id: <166428358688.365276.7811132471034976434.b4-ty@kernel.org> Date: Tue, 27 Sep 2022 13:59:46 +0100 From: Mark Brown <broonie@...nel.org> To: Bard Liao <yung-chuan.liao@...ux.intel.com>, Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>, Takashi Iwai <tiwai@...e.com>, Cezary Rojewski <cezary.rojewski@...el.com>, Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>, Kai Vehmanen <kai.vehmanen@...ux.intel.com>, "Gustavo A. R. Silva" <gustavoars@...nel.org>, Peter Ujfalusi <peter.ujfalusi@...ux.intel.com>, Jaroslav Kysela <perex@...ex.cz>, Liam Girdwood <liam.r.girdwood@...ux.intel.com> Cc: linux-hardening@...r.kernel.org, linux-kernel@...r.kernel.org, alsa-devel@...a-project.org Subject: Re: [PATCH][next] ASoC: Intel: Skylake: Replace zero-length arrays with DECLARE_FLEX_ARRAY() helper On Mon, 26 Sep 2022 17:58:17 -0500, Gustavo A. R. Silva wrote: > Zero-length arrays are deprecated and we are moving towards adopting > C99 flexible-array members, instead. So, replace zero-length arrays > declarations in anonymous union with the new DECLARE_FLEX_ARRAY() > helper macro. > > This helper allows for flexible-array members in unions. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/1] ASoC: Intel: Skylake: Replace zero-length arrays with DECLARE_FLEX_ARRAY() helper commit: 6fed3265c3c811c79819860051375f6d7efc1d7e 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
Powered by blists - more mailing lists