linux-kernel - Re: [PATCH 0/2] firmware: cs_dsp: Switch to using namespaced exports

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: <166938710147.543323.1489768823749219688.b4-ty@kernel.org>
Date:   Fri, 25 Nov 2022 14:38:21 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Richard Fitzgerald <rf@...nsource.cirrus.com>, tiwai@...e.com
Cc:     linux-kernel@...r.kernel.org, alsa-devel@...a-project.org,
        patches@...nsource.cirrus.com
Subject: Re: [PATCH 0/2] firmware: cs_dsp: Switch to using namespaced exports

On Thu, 24 Nov 2022 13:45:54 +0000, Richard Fitzgerald wrote:
> Use EXPORT_SYMBOL_NS_GPL() instead of EXPORT_SYMBOL_GPL() and patch the
> three drivers that use cs_dsp to add the MODULE_IMPORT_NS().
> 
> To make the namespace more specific the KConfig symbol for cs_dsp is
> changed from CS_DSP to FW_CS_DSP.
> 
> Richard Fitzgerald (2):
>   firmware: cs_dsp: Rename KConfig symbol CS_DSP -> FW_CS_DSP
>   firmware: cs_dsp: Make the exports namespaced
> 
> [...]

Applied to

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

Thanks!

[1/2] firmware: cs_dsp: Rename KConfig symbol CS_DSP -> FW_CS_DSP
      commit: d7cfdf17cb9d072b41547e7cc882ecd900aa6589
[2/2] firmware: cs_dsp: Make the exports namespaced
      commit: e57d904ac4be6de7ecc9083f51a9a38f72482f82

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