linux-kernel - Re: [PATCH] ASoC: tegra: Fix MBDRC bypass mode check

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:   Wed, 15 Jun 2022 14:54:34 +0100
From:   Mark Brown <broonie@...nel.org>
To:     spujar@...dia.com, dan.carpenter@...cle.com, perex@...ex.cz,
        tiwai@...e.com
Cc:     linux-kernel@...r.kernel.org, jonathanh@...dia.com,
        linux-tegra@...r.kernel.org, alsa-devel@...a-project.org,
        thierry.reding@...il.com
Subject: Re: [PATCH] ASoC: tegra: Fix MBDRC bypass mode check

On Wed, 15 Jun 2022 10:08:34 +0530, Sameer Pujar wrote:
> MBDRC supports different modes of operation. There is no configuration
> required for bypass mode. The hw_params() call does not filter bypass
> mode correctly and it leads to following Smatch static checker warning:
> 
>   sound/soc/tegra/tegra210_mbdrc.c:778 tegra210_mbdrc_hw_params()
>   warn: bitwise AND condition is false here
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: tegra: Fix MBDRC bypass mode check
      commit: 4edf738d4c7989c315e37d4d61e34c94557b6ed2

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