linux-kernel - Re: [PATCH 1/2] ASoC: amd: ps: update macros with ps platform naming convention

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: <166860995741.526370.1821465531343150450.b4-ty@kernel.org>
Date:   Wed, 16 Nov 2022 14:45:57 +0000
From:   Mark Brown <broonie@...nel.org>
To:     alsa-devel@...a-project.org,
        Syed Saba Kareem <Syed.SabaKareem@....com>
Cc:     Liam Girdwood <lgirdwood@...il.com>,
        open list <linux-kernel@...r.kernel.org>,
        Sunil-kumar.Dommati@....com, mario.limonciello@....com,
        Vijendar.Mukunda@....com, Jaroslav Kysela <perex@...ex.cz>,
        Takashi Iwai <tiwai@...e.com>, Basavaraj.Hiregoudar@....com
Subject: Re: [PATCH 1/2] ASoC: amd: ps: update macros with ps platform naming convention

On Wed, 16 Nov 2022 16:29:22 +0530, Syed Saba Kareem wrote:
> Update macros using ps platform naming convention.
> 
> 

Applied to

   broonie/sound.git for-next

Thanks!

[1/2] ASoC: amd: ps: update macros with ps platform naming convention
      commit: d25ec74c6c5419f834bab506f251bc760bdfb858
[2/2] ASoC: amd: ps: Move acp63_dev_data strcture from PCI driver
      commit: 7d95977533e14738e8193c14a7efac369288aeee

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