[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <169462719996.54382.1348437312266956494.b4-ty@kernel.org>
Date: Wed, 13 Sep 2023 18:46:39 +0100
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, pierre-louis.bossart@...ux.intel.com,
tiwai@...e.com, perex@...ex.cz, arnd@...db.de,
Peter Ujfalusi <peter.ujfalusi@...ux.intel.com>
Cc: alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
masahiroy@...nel.org
Subject: Re: [PATCH] ASoC: hdac_hdmi: Remove temporary string use in
create_fill_jack_kcontrols
On Wed, 13 Sep 2023 12:13:25 +0300, Peter Ujfalusi wrote:
> There is no need to use temporary strings to construct the kcontrol names,
> devm_kasprintf can be used to replace the snprintf + devm_kstrdup pairs.
>
> This change will also fixes the following compiler warning/error (W=1):
>
> sound/soc/codecs/hdac_hdmi.c: In function ‘hdac_hdmi_jack_port_init’:
> sound/soc/codecs/hdac_hdmi.c:1793:63: error: ‘ Switch’ directive output may be truncated writing 7 bytes into a region of size between 1 and 32 [-Werror=format-truncation=]
> 1793 | snprintf(kc_name, sizeof(kc_name), "%s Switch", xname);
> | ^~~~~~~
> In function ‘create_fill_jack_kcontrols’,
> inlined from ‘hdac_hdmi_jack_port_init’ at sound/soc/codecs/hdac_hdmi.c:1871:8:
> sound/soc/codecs/hdac_hdmi.c:1793:25: note: ‘snprintf’ output between 8 and 39 bytes into a destination of size 32
> 1793 | snprintf(kc_name, sizeof(kc_name), "%s Switch", xname);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> cc1: all warnings being treated as errors
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: hdac_hdmi: Remove temporary string use in create_fill_jack_kcontrols
commit: 67a810b6f37a7805474add2d003034a288b94fa4
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