linux-kernel - Re: [PATCH 1/3] ASoC: amd: ps: add mutex lock for accessing common registers

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: <167302468725.215080.6874492373066173949.b4-ty@kernel.org>
Date:   Fri, 06 Jan 2023 17:04:47 +0000
From:   Mark Brown <broonie@...nel.org>
To:     alsa-devel@...a-project.org, syed.sabakareem@....com,
        Vijendar Mukunda <Vijendar.Mukunda@....com>
Cc:     Sunil-kumar.Dommati@....com, mario.limonciello@....com,
        basavaraj.hiregoudar@....com, Liam Girdwood <lgirdwood@...il.com>,
        Jaroslav Kysela <perex@...ex.cz>,
        Takashi Iwai <tiwai@...e.com>,
        Syed Saba Kareem <Syed.SabaKareem@....com>,
        open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/3] ASoC: amd: ps: add mutex lock for accessing common registers

On Wed, 04 Jan 2023 11:24:29 +0530, Vijendar Mukunda wrote:
> Add mutex lock for accessing ACP common registers across different
> modules.
> 
> 

Applied to

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

Thanks!

[1/3] ASoC: amd: ps: add mutex lock for accessing common registers
      commit: f763fb2fc93065d33f17fe9c5adeac8dec7713dc
[2/3] ASoC: amd: ps: use acp_lock to protect common registers in pdm driver
      commit: 45aa83cb93885d406c178498623b01cf128ca233
[3/3] ASoC: amd: ps: remove unused variable
      commit: 948f317fac06f8c0e2dea8c37f5ae5ee10514034

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