ASoC: cs-amp-lib-test: Use flex_array_size()
Subsystems (3)
Richard Fitzgerald
maintainerPATCH 1/1 ASoC: cs-amp-lib-test: Use flex_array_size()
Use flex_array_size() when calculating the number of bytes argument to get_random_bytes(). This replaces a calculation based on passing sizeof() the expected type of the destination.
--- sound/soc/codecs/cs-amp-lib-test.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
sound/soc/codecs/cs-amp-lib-test.c +1 -1
@@ -54,7 +54,7 @@ static void cs_amp_lib_test_init_dummy_cal_blob(struct kunit *test, int num_amps priv->cal_blob->size = blob_size; priv->cal_blob->count = num_amps; -get_random_bytes (priv->cal_blob->data,sizeof (struct cirrus_amp_cal_data ) * num_amps); +get_random_bytes (priv->cal_blob->data,flex_array_size (priv->cal_blob, data, num_amps));/* Ensure all timestamps are non-zero to mark the entry valid. */ for (i =0 ; i < num_amps; i++)
Signature · 1 line
2.39.5
Mark Brown
maintainerQuoted 5 lines · Richard Fitzgerald
Use
flex_array_size()when calculating the number of bytes argument toget_random_bytes(). This replaces a calculation based on passingsizeof()the expected type of the destination.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: cs-amp-lib-test: Use flex_array_size()
commit: 51f04358d8c887c5d117440335c7f94285a403f2
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