[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <168916243923.46574.4640392228923703244.b4-ty@kernel.org>
Date: Wed, 12 Jul 2023 12:47:19 +0100
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>,
Syed Saba Kareem <Syed.SabaKareem@....com>,
Vijendar Mukunda <Vijendar.Mukunda@....com>,
Arnd Bergmann <arnd@...db.de>,
Randy Dunlap <rdunlap@...radead.org>,
Charles Keepax <ckeepax@...nsource.cirrus.com>,
Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
Cristian Ciocaltea <cristian.ciocaltea@...labora.com>
Cc: alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
kernel@...labora.com
Subject: Re: [PATCH v3 0/3] AMD Vangogh support for NAU8821/MAX98388
On Thu, 06 Jul 2023 00:47:57 +0300, Cristian Ciocaltea wrote:
> This patch series extends the Vangogh machine driver to support a variant
> based on the Nuvoton NAU88L21 Codec and the Analog Devices MAX98388
> Speaker Amplifier.
>
> Changes in v3:
> * Dropped acp5x_max98388_hw_params() in PATCH 3/3 and rely on dai_link
> to set format, according to Mark's review
> * v2: https://lore.kernel.org/all/20230705134341.175889-1-cristian.ciocaltea@collabora.com/
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/3] ASoC: amd: vangogh: Make use of DRV_NAME
commit: a0cb05cb70b469198ad86c0b13b02cbba3ecd8fd
[2/3] ASoC: amd: vangogh: Use dmi_first_match() for DMI quirk handling
commit: 3dd26e27ccb4f18b4d25c0a49e1888eca9c6a724
[3/3] ASoC: amd: vangogh: Add support for NAU8821/MAX98388 variant
commit: dba22efd0d177a23c6da2a161e9a1ad29718924c
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