linux-kernel - Re: [PATCH] ASoC: amd: yc: Add VivoBook Pro 15 to quirks list for acp6x

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: <169262762417.266100.4223916224469728296.b4-ty@kernel.org>
Date:   Mon, 21 Aug 2023 15:20:24 +0100
From:   Mark Brown <broonie@...nel.org>
To:     BrenoRCBrito <brenorcbrito@...il.com>
Cc:     Liam Girdwood <lgirdwood@...il.com>,
        Jaroslav Kysela <perex@...ex.cz>,
        Takashi Iwai <tiwai@...e.com>,
        Mario Limonciello <mario.limonciello@....com>,
        Syed Saba Kareem <Syed.SabaKareem@....com>,
        linkt <xazrael@...mail.com>, alsa-devel@...a-project.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: amd: yc: Add VivoBook Pro 15 to quirks list for
 acp6x

On Fri, 18 Aug 2023 18:14:16 -0300, BrenoRCBrito wrote:
> VivoBook Pro 15 Ryzen Edition uses Ryzen 6800H processor, and adding to
>  quirks list for acp6x will enable internal mic.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: amd: yc: Add VivoBook Pro 15 to quirks list for acp6x
      commit: 3b1f08833c45d0167741e4097b0150e7cf086102

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