linux-kernel - Re: [PATCH 0/1] Add support for primary mi2s on SM8250

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: <172607056132.105227.11889587704269825553.b4-ty@kernel.org>
Date: Wed, 11 Sep 2024 17:02:41 +0100
From: Mark Brown <broonie@...nel.org>
To: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>, 
 Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, Jens Reidel <adrian@...vitia.xyz>
Cc: alsa-devel@...a-project.org, linux-arm-msm@...r.kernel.org, 
 linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 linux@...nlining.org
Subject: Re: [PATCH 0/1] Add support for primary mi2s on SM8250

On Mon, 26 Aug 2024 15:49:19 +0200, Jens Reidel wrote:
> This patch adds support for the primary mi2s interface on devices using SM8250
> audio drivers. Tested on SM7150 (xiaomi-davinci). SM7150 sound is close to
> SM8250 and we intend to use it as a fallback in the future.
> 
> To: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
> To: Liam Girdwood <lgirdwood@...il.com>
> To: Mark Brown <broonie@...nel.org>
> To: Jaroslav Kysela <perex@...ex.cz>
> To: Takashi Iwai <tiwai@...e.com>
> Cc: alsa-devel@...a-project.org
> Cc: linux-arm-msm@...r.kernel.org
> Cc: linux-sound@...r.kernel.org
> Cc: linux-kernel@...r.kernel.org
> Cc: linux@...nlining.org
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: qcom: sm8250: enable primary mi2s
      commit: 851e3a2a4490b03bb8dd0cda1b8b2a78f6a92805

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