public inbox for regressions@lists.linux.dev
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: "kailang@realtek.com" <kailang@realtek.com>,
	Takashi Iwai <tiwai@suse.de>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
	"tiwai@suse.com" <tiwai@suse.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"perex@perex.cz" <perex@perex.cz>,
	Ruslan Nikolaev <nruslan_devel@yahoo.com>,
	Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [Bug 220109] New: Audio disappears on HP 15-fc000 after warm boot again (ALC256 code path)
Date: Thu, 6 Nov 2025 10:11:29 -0500	[thread overview]
Message-ID: <aQy6oUX7THK_VhqO@laps> (raw)
In-Reply-To: <e182047c-ed7c-4fb1-bd61-fc0536b12b2e@leemhuis.info>

On Thu, Nov 06, 2025 at 10:34:44AM +0100, Thorsten Leemhuis wrote:
>Hi, top-posting for once, to make this easily accessible to everyone.
>
>@Kailang, @Takashi: The fix for the mainline/6.12.y regression this
>thread is about was afaics merged for v6.17-rc3 as f4b3cef55f5f96
>("ALSA: hda/realtek: Audio disappears on HP 15-fc000 after warm boot
>again").
>
>Greg's scripts despite the Fixes-tag for some reason did not backport it
>to various series that contain the culprit. Is there a reason for that?
>Otherwise we likely should ask Greg to pick it up.

We didn't pick it up because it doesn't apply to 6.12 or prior, nor is there a
stable tag on that commit :)

I'll backport it to older trees and queue it up.

-- 
Thanks,
Sasha

      reply	other threads:[~2025-11-06 15:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1064773772.509063.1747061777318.ref@mail.yahoo.com>
2025-05-12 14:56 ` Fwd: [Bug 220109] New: Audio disappears on HP 15-fc000 after warm boot again (ALC256 code path) Ruslan Nikolaev
2025-05-12 15:06   ` Takashi Iwai
2025-05-13  4:36     ` Ruslan Nikolaev
2025-11-06  9:34       ` Thorsten Leemhuis
2025-11-06 15:11         ` Sasha Levin [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=aQy6oUX7THK_VhqO@laps \
    --to=sashal@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kailang@realtek.com \
    --cc=nruslan_devel@yahoo.com \
    --cc=perex@perex.cz \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=tiwai@suse.com \
    --cc=tiwai@suse.de \
    /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