linux-kernel - Re: [PATCH] firmware: cs_dsp: Log correct region name in bin error messages

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: <168605251548.20864.13850925270775082245.b4-ty@kernel.org>
Date:   Tue, 06 Jun 2023 12:55:15 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc:     alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
        patches@...nsource.cirrus.com
Subject: Re: [PATCH] firmware: cs_dsp: Log correct region name in bin error
 messages

On Mon, 05 Jun 2023 15:32:38 +0100, Richard Fitzgerald wrote:
> In cs_dsp_load_coeff() region_name should be set in the XM/YM/ZM
> cases otherwise any errors will log the region as "Unknown".
> 
> While doing this also change one error message that logged the
> region type ID to log the region_name instead. This makes it
> consistent with other messages in the same function.
> 
> [...]

Applied to

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

Thanks!

[1/1] firmware: cs_dsp: Log correct region name in bin error messages
      commit: ad24919540fb4df83981d469b5253cc1aecca939

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