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: <165947207673.2174889.4273360535834711916.b4-ty@kernel.org>
Date:   Tue, 02 Aug 2022 21:27:56 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Syed Saba Kareem <Syed.SabaKareem@....com>,
        alsa-devel@...a-project.org
Cc:     Vijendar.Mukunda@....com,
        Pananchikkal Renjith <renjith.pananchikkal@....com>,
        Liam Girdwood <lgirdwood@...il.com>,
        Takashi Iwai <tiwai@...e.com>,
        Mario Limonciello <mario.limonciello@....com>,
        Jaroslav Kysela <perex@...ex.cz>, Sunil-kumar.Dommati@....com,
        Basavaraj.Hiregoudar@....com,
        open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ASoC: amd: yc: Update DMI table entries for AMD platforms

On Tue, 2 Aug 2022 11:55:00 +0530, Syed Saba Kareem wrote:
> From: syed sabakareem <Syed.SabaKareem@....com>
> 
> Updated DMI entries 21EM, 21EN, 21J5 and 21J6 for
> AMD platforms P15v Gen 3 and P14s Gen 3.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: amd: yc: Update DMI table entries for AMD platforms
      commit: c0fc96fed7ffa3e58f58b9cdb7158b5c61e026a2

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ