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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 2 Oct 2021 01:16:32 +0100 From: Mark Brown <broonie@...nel.org> To: Brent Lu <brent.lu@...el.com>, alsa-devel@...a-project.org Cc: Mark Brown <broonie@...nel.org>, linux-kernel@...r.kernel.org, Rander Wang <rander.wang@...el.com>, Malik_Hsu <malik_hsu@...tron.corp-partner.google.com>, Guennadi Liakhovetski <guennadi.liakhovetski@...ux.intel.com>, Kai Vehmanen <kai.vehmanen@...ux.intel.com>, Jie Yang <yang.jie@...ux.intel.com>, Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>, Takashi Iwai <tiwai@...e.com>, Bard Liao <bard.liao@...el.com>, Libin Yang <libin.yang@...el.com>, Tzung-Bi Shih <tzungbi@...gle.com>, Cezary Rojewski <cezary.rojewski@...el.com>, Vamshi Krishna Gopal <vamshi.krishna.gopal@...el.com>, Yong Zhi <yong.zhi@...el.com>, Jaroslav Kysela <perex@...ex.cz>, Liam Girdwood <liam.r.girdwood@...ux.intel.com> Subject: Re: [PATCH] ASoC: Intel: sof_rt5682: Add support for max98360a speaker amp On Fri, 1 Oct 2021 23:03:16 +0800, Brent Lu wrote: > From: Malik_Hsu <malik_hsu@...tron.corp-partner.google.com> > > Add a board config adl_mx98360a_rt5682 to support alc5682 headset > codec and max98360a speaker amplifier. Follow Intel BT offload design > by connecting alc5682 to SSP0 and max98360a to SSP1. > > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/1] ASoC: Intel: sof_rt5682: Add support for max98360a speaker amp commit: 9c892547624ff277546a9d4fede3d95259e6faea 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