linux-kernel - Re: [PATCH] ASoC: amd: acp: declare and add prefix to 'bt_uart

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]

Date:   Mon, 13 Sep 2021 11:53:15 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
        alsa-devel@...a-project.org
Cc:     Mark Brown <broonie@...nel.org>, Jaroslav Kysela <perex@...ex.cz>,
        Chuhong Yuan <hslester96@...il.com>,
        Gu Shengxian <gushengxian@...ong.com>,
        Liam Girdwood <lgirdwood@...il.com>,
        Mario Limonciello <mario.limonciello@....com>,
        open list <linux-kernel@...r.kernel.org>, tiwai@...e.de,
        Vijendar Mukunda <Vijendar.Mukunda@....com>,
        Takashi Iwai <tiwai@...e.com>
Subject: Re: [PATCH] ASoC: amd: acp: declare and add prefix to 'bt_uart_enable' symbol

On Tue, 7 Sep 2021 13:42:14 -0500, Pierre-Louis Bossart wrote:
> Sparse reports the following warning:
> 
> sound/soc/amd/acp-pcm-dma.c:39:6: error: symbol 'bt_uart_enable' was
> not declared. Should it be static?
> 
> It's not very good practice to export such symbols that can easily
> conflict, add the acp_ prefix and add declaration in header file.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: amd: acp: declare and add prefix to 'bt_uart_enable' symbol
      commit: 198433023ef962b71f3d4274ca7a4c8f04e7ace1

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