linux-kernel - Re: [PATCH 0/2] ASoC/SoundWire: Simply interrupt enabling for Intel

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: <172873744520.3950734.5770397473019892080.b4-ty@kernel.org>
Date: Sat, 12 Oct 2024 13:50:45 +0100
From: Mark Brown <broonie@...nel.org>
To: tiwai@...e.de, vkoul@...nel.org, 
 Bard Liao <yung-chuan.liao@...ux.intel.com>
Cc: vinod.koul@...aro.org, linux-kernel@...r.kernel.org, 
 linux-sound@...r.kernel.org, pierre-louis.bossart@...ux.dev, 
 bard.liao@...el.com, peter.ujfalusi@...ux.intel.com
Subject: Re: [PATCH 0/2] ASoC/SoundWire: Simply interrupt enabling for
 Intel

On Mon, 07 Oct 2024 20:12:39 +0800, Bard Liao wrote:
> It is more logical to couple interrupt enabling/disabling with
> power-up/down sequences.
> 
> The change is mainly on ASoC tree. Can we go via ASoC tree with Vinod's
> Acked-by tag?
> 
> Pierre-Louis Bossart (2):
>   ASoC: SOF: Intel: hda-mlink: expose unlocked interrupt enable routine
>   ASoC/SoundWire: Intel: lnl: enable interrupts after first
>     power-up/before last power-down
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: SOF: Intel: hda-mlink: expose unlocked interrupt enable routine
      commit: eac79786c7397925149a1bfc4bb704777cd42a99
[2/2] ASoC/SoundWire: Intel: lnl: enable interrupts after first power-up/before last power-down
      commit: e0941775e6bdcf45e6e20b7ff3bb87dbb7d92fbb

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