linux-kernel - Re: [PATCH] ASoC: amd: fix ACP version typo mistake

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: <166757697041.399796.7667715854379542495.b4-ty@kernel.org>
Date:   Fri, 04 Nov 2022 15:49:30 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Syed Saba Kareem <Syed.SabaKareem@....com>,
        alsa-devel@...a-project.org
Cc:     syed saba kareem <syed.sabakareem@....com>,
        Basavaraj.Hiregoudar@....com, Liam Girdwood <lgirdwood@...il.com>,
        Vijendar.Mukunda@....com,
        Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
        mario.limonciello@....com, Sunil-kumar.Dommati@....com,
        Takashi Iwai <tiwai@...e.com>,
        Daniel Baluta <daniel.baluta@....com>,
        Jaroslav Kysela <perex@...ex.cz>,
        Ajit Kumar Pandey <AjitKumar.Pandey@....com>,
        Lucas Tanure <tanureal@...nsource.cirrus.com>,
        Randy Dunlap <rdunlap@...radead.org>,
        open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ASoC: amd: fix ACP version typo mistake

On Fri, 4 Nov 2022 17:39:07 +0530, Syed Saba Kareem wrote:
> From: syed saba kareem <syed.sabakareem@....com>
> 
> Pink Sardine is based on ACP6.3 architecture.
> This patch fixes the typo mistake acp6.2 -> acp6.3
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: amd: fix ACP version typo mistake
      commit: 4b19211435950a78af032c26ad64a5268e6012be

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