linux-kernel - Re: [PATCH] ASoC: wm_adsp: Minor clean and redundant code removal

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: <165660181820.664251.9414397371469322240.b4-ty@kernel.org>
Date:   Thu, 30 Jun 2022 16:10:18 +0100
From:   Mark Brown <broonie@...nel.org>
To:     ckeepax@...nsource.cirrus.com
Cc:     alsa-devel@...a-project.org, patches@...nsource.cirrus.com,
        linux-kernel@...r.kernel.org, lgirdwood@...il.com
Subject: Re: [PATCH] ASoC: wm_adsp: Minor clean and redundant code removal

On Thu, 30 Jun 2022 11:14:59 +0100, Charles Keepax wrote:
> The cs_dsp core will return an error if passed a NULL cs_dsp struct so
> there is no need for the wm_adsp_write|read_ctl functions to manually
> check that. The cs_dsp core will also check the data is within bounds of
> the control so the additional bounds check is redundant too. Simplify
> things a bit by removing said code.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: wm_adsp: Minor clean and redundant code removal
      commit: e8010efc7b83038d1c18abe1b8d171e3c7d4ed92

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