The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Tommaso Zanotti <kernel@tomzanna.com>
To: broonie@kernel.org
Cc: Basavaraj.Hiregoudar@amd.com, Sunil-kumar.Dommati@amd.com,
	Syed.SabaKareem@amd.com, Vijendar.Mukunda@amd.com,
	alsa-devel@alsa-project.org, bagasdotme@gmail.com,
	kuninori.morimoto.gx@renesas.com, lgirdwood@gmail.com,
	linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
	mario.limonciello@amd.com, nicolas.ferre@microchip.com,
	perex@perex.cz, posteuca@mutex.one, tiwai@suse.com,
	u.kleine-koenig@pengutronix.de, venkataprasad.potturu@amd.com
Subject: Re: [RESEND] ASoC: amd: acp: add pm ops support for renoir platform.
Date: Wed, 27 Dec 2023 11:42:09 +0100	[thread overview]
Message-ID: <20231227104209.6281-1-kernel@tomzanna.com> (raw)
In-Reply-To: <170267843699.316482.4350897389116089852.b4-ty@kernel.org>

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



      reply	other threads:[~2023-12-27 11:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-15 13:02 [RESEND] ASoC: amd: acp: add pm ops support for renoir platform Syed Saba Kareem
2023-12-15 14:46 ` Mario Limonciello
2023-12-15 22:13 ` Mark Brown
2023-12-27 10:42   ` Tommaso Zanotti [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20231227104209.6281-1-kernel@tomzanna.com \
    --to=kernel@tomzanna.com \
    --cc=Basavaraj.Hiregoudar@amd.com \
    --cc=Sunil-kumar.Dommati@amd.com \
    --cc=Syed.SabaKareem@amd.com \
    --cc=Vijendar.Mukunda@amd.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=bagasdotme@gmail.com \
    --cc=broonie@kernel.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=nicolas.ferre@microchip.com \
    --cc=perex@perex.cz \
    --cc=posteuca@mutex.one \
    --cc=tiwai@suse.com \
    --cc=u.kleine-koenig@pengutronix.de \
    --cc=venkataprasad.potturu@amd.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox