linux-kernel - Re: [PATCH] ASoC: rt5663: Handle device_property_read_u32

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <163959205325.2218314.11285157350197840732.b4-ty@kernel.org>
Date:   Wed, 15 Dec 2021 18:14:13 +0000
From:   Mark Brown <broonie@...nel.org>
To:     oder_chiou@...ltek.com, Jiasheng Jiang <jiasheng@...as.ac.cn>,
        lgirdwood@...il.com, tiwai@...e.com, perex@...ex.cz
Cc:     linux-kernel@...r.kernel.org, alsa-devel@...a-project.org
Subject: Re: [PATCH] ASoC: rt5663: Handle device_property_read_u32_array error codes

On Wed, 15 Dec 2021 11:15:50 +0800, Jiasheng Jiang wrote:
> The return value of device_property_read_u32_array() is not always 0.
> To catch the exception in case that devm_kzalloc failed and the
> rt5663->imp_table was NULL, which caused the failure of
> device_property_read_u32_array.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: rt5663: Handle device_property_read_u32_array error codes
      commit: 2167c0b205960607fb136b4bb3c556a62be1569a

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