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]
Date:   Wed, 21 Sep 2022 10:25:04 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Mario Limonciello <mario.limonciello@....com>
Cc:     Saba Kareem Syed <Syed.SabaKareem@....com>,
        Sebastian S <iam@...entr.al>, linux-kernel@...r.kernel.org,
        alsa-devel@...a-project.org, Xiaoyan Li <lxy.lixiaoyan@...il.com>,
        Travis Glenn Hansen <travisghansen@...oo.com>
Subject: Re: [PATCH v2 0/2] Add some models into acp6x quirk list

On Tue, 20 Sep 2022 14:46:19 -0500, Mario Limonciello wrote:
> Another model from ASUS and Lenovo have been identified that
> don't include anything in ACPI tables to indicate they require the
> ACP6x DMIC driver to be loaded.
> 
> This series adds them both to the quirk list.
> 
> changes from v1->v2:
>  * Both models were independently sent in v1 but touch the same code,
>    so v2 collates them together.
> 
> [...]

Applied to

   broonie/sound.git for-next

Thanks!

[1/2] ASoC: amd: yc: Add ASUS UM5302TA into DMI table
      commit: 4df5b13dec9e1b5a12db47ee92eb3f7da5c3deb5
[2/2] ASoC: amd: yc: Add Lenovo Yoga Slim 7 Pro X to quirks table
      commit: 2232b2dd8cd4f1e6d554b2c3f6899ce36f791b67

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