linux-kernel - Re: [PATCH] ASoC: wcd9335: Keep a RX port value for each SLIM RX mux

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:   Thu, 06 Jan 2022 20:28:20 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Jaroslav Kysela <perex@...ex.cz>, alsa-devel@...a-project.org,
        Yassine Oudjana <y.oudjana@...tonmail.com>,
        Takashi Iwai <tiwai@...e.com>,
        Banajit Goswami <bgoswami@...eaurora.org>,
        Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc:     linux-kernel@...r.kernel.org, Liam Girdwood <lgirdwood@...il.com>
Subject: Re: [PATCH] ASoC: wcd9335: Keep a RX port value for each SLIM RX mux

On Tue, 04 Jan 2022 03:35:36 +0000, Yassine Oudjana wrote:
> Currently, rx_port_value is a single unsigned int that gets overwritten
> when slim_rx_mux_put() is called for any RX mux, then the same value is
> read when slim_rx_mux_get() is called for any of them. This results in
> slim_rx_mux_get() reporting the last value set by slim_rx_mux_put()
> regardless of which SLIM RX mux is in question.
> 
> Turn rx_port_value into an array and store a separate value for each
> SLIM RX mux.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: wcd9335: Keep a RX port value for each SLIM RX mux
      commit: 3b247eeaecfefe35ecca1578b0ed48be65bc6ca3

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