linux-kernel - Re: [RESEND] ASoC: amd: acp: add pm ops support for renoir platform.

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: <20231227104209.6281-1-kernel@tomzanna.com>
Date: Wed, 27 Dec 2023 11:42:09 +0100
From: Tommaso Zanotti <kernel@...zanna.com>
To: broonie@...nel.org
Cc: Basavaraj.Hiregoudar@....com,
	Sunil-kumar.Dommati@....com,
	Syed.SabaKareem@....com,
	Vijendar.Mukunda@....com,
	alsa-devel@...a-project.org,
	bagasdotme@...il.com,
	kuninori.morimoto.gx@...esas.com,
	lgirdwood@...il.com,
	linux-kernel@...r.kernel.org,
	linux-sound@...r.kernel.org,
	mario.limonciello@....com,
	nicolas.ferre@...rochip.com,
	perex@...ex.cz,
	posteuca@...ex.one,
	tiwai@...e.com,
	u.kleine-koenig@...gutronix.de,
	venkataprasad.potturu@....com
Subject: Re: [RESEND] ASoC: amd: acp: add pm ops support for renoir platform.

Hi Marc,
first time writing on a kernel mailing list here.

> 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)

I noticed that this patch is scheduled to land in mainline on 6.8.
However, it was the second of a two-part bugfix for a regression introduced
in 6.6-rc1. You can find more info here:
- https://lore.kernel.org/lkml/87a5v8szhc.fsf@mutex.one/
- https://linux-regtracking.leemhuis.info/regzbot/regression/lore/87a5v8szhc.fsf@mutex.one/

Would be feasible to ship this patch already in the next 6.7-rc?
Because with the stable 6.7 some Huawei laptops will finally receive audio
support but due to this regression a workaround in user space is necessary.

Cheers,
Tommaso