linux-kernel - Re: [PATCH 0/2] firmware: cs_dsp: Cleanup debugfs for wmfw and bin file name

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: <176373448817.9116.11357878352484570206.b4-ty@kernel.org>
Date: Fri, 21 Nov 2025 14:14:48 +0000
From: Mark Brown <broonie@...nel.org>
To: Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 patches@...nsource.cirrus.com
Subject: Re: [PATCH 0/2] firmware: cs_dsp: Cleanup debugfs for wmfw and bin
 file name

On Thu, 20 Nov 2025 13:06:38 +0000, Richard Fitzgerald wrote:
> These two patches improve the implementation of the debugfs files for
> the wmfw and bin file names. First patch removes duplicated code. Second
> patch replaces the old clunkiness of storing the filename with an appended
> \n. The \n can be appended when the file is read, to keep the stored string
> sane.
> 
> Richard Fitzgerald (2):
>   firmware: cs_dsp: Factor out common debugfs string read
>   firmware: cs_dsp: Append \n to debugfs string during read
> 
> [...]

Applied to

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

Thanks!

[1/2] firmware: cs_dsp: Factor out common debugfs string read
      commit: 78cfd833bc04c0398ca4cfc64704350aebe4d4c2
[2/2] firmware: cs_dsp: Append \n to debugfs string during read
      commit: 3045e29d248bde2a68da425498a656093ee0df69

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