linux-kernel - Re: [PATCH 1/5] ASoC: amd: add RPL Platform acp header file

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <165849409858.139149.7568411438322284849.b4-ty@kernel.org>
Date:   Fri, 22 Jul 2022 13:48:18 +0100
From:   Mark Brown <broonie@...nel.org>
To:     alsa-devel@...a-project.org,
        syed sabakareem <Syed.SabaKareem@....com>
Cc:     Sunil-kumar.Dommati@....com, Alexander.Deucher@....com,
        vijendar.mukunda@....com, Takashi Iwai <tiwai@...e.com>,
        open list <linux-kernel@...r.kernel.org>,
        Basavaraj.Hiregoudar@....com,
        Vijendar Mukunda <Vijendar.Mukunda@....com>,
        Liam Girdwood <lgirdwood@...il.com>,
        Jaroslav Kysela <perex@...ex.cz>
Subject: Re: [PATCH 1/5] ASoC: amd: add RPL Platform acp header file

On Thu, 21 Jul 2022 11:39:58 +0530, syed sabakareem wrote:
> From: Syed Saba Kareem <Syed.SabaKareem@....com>
> 
> Add ACP register header file for RPL platform.
> 
> 

Applied to

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

Thanks!

[1/5] ASoC: amd: add RPL Platform acp header file
      commit: d6a2cc9a80c2fdc10f7fde3f5f57c72e99f3bd5e
[2/5] ASoC: amd: add ACP PCI driver for RPL platform
      commit: 003b9a96f27635e534452b174733c5f1ceec0b56
[3/5] ASoC: amd: add RPL Platform init/de-init functions
      commit: 10599205417ee3b1d29093c85bc210c9040a6bd4
[4/5] ASoC: amd: add RPL Platform pci driver pm-ops
      commit: bc1100f29d1d0bfcd36ba3690a945235ffe149c8
[5/5] ASoC: amd: enable RPL Platform acp drivers build
      commit: 4fb35936a374758d5065b0a015c565436685c378

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