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
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Sat,  2 Oct 2021 01:16:32 +0100
From:   Mark Brown <>
To:     Brent Lu <>,
Cc:     Mark Brown <>,,
        Rander Wang <>,
        Malik_Hsu <>,
        Guennadi Liakhovetski <>,
        Kai Vehmanen <>,
        Jie Yang <>,
        Pierre-Louis Bossart <>,
        Takashi Iwai <>, Bard Liao <>,
        Libin Yang <>,
        Tzung-Bi Shih <>,
        Cezary Rojewski <>,
        Vamshi Krishna Gopal <>,
        Yong Zhi <>,
        Jaroslav Kysela <>,
        Liam Girdwood <>
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 <>
> 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 for-next


[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.


Powered by blists - more mailing lists