From: Takashi Iwai <tiwai@suse.de>
To: Askar Safin <safinaskar@gmail.com>
Cc: "Takashi Iwai" <tiwai@suse.de>,
Dell.Client.Kernel@dell.com, amadeuszx.slawinski@linux.intel.com,
baojun.xu@ti.com, bo.liu@senarytech.com,
cezary.rojewski@intel.com, kai.vehmanen@linux.intel.com,
kailang@realtek.com, linux-sound@vger.kernel.org,
patches@opensource.cirrus.com, regressions@lists.linux.dev,
rf@opensource.cirrus.com, "Nicolas Schier" <nsc@kernel.org>,
linux-kbuild@vger.kernel.org,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Nathan Chancellor" <nathan@kernel.org>,
miguel.ojeda.sandonis@gmail.com, ojeda@kernel.org,
sam@gentoo.org,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"Daniel Xu" <dxu@dxuuu.xyz>
Subject: Re: [REGRESSION][BISECTED] My audio broke (was: [PATCH 05/27] ALSA: hda: Move controller drivers into sound/hda/controllers directory)
Date: Wed, 10 Dec 2025 14:00:13 +0100 [thread overview]
Message-ID: <87345iebky.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAPnZJGCknqB3XjNY5zhD7i84pz+uL+v4OUgw04ADxR-W=CAeGA@mail.gmail.com>
On Wed, 10 Dec 2025 02:45:55 +0100,
Askar Safin wrote:
>
> On Tue, Dec 9, 2025 at 12:27 PM Takashi Iwai <tiwai@suse.de> wrote:
> > The below one is a revised fix, just to be safer in case the legacy
> > driver is disabled, too. Give it a try.
>
> I just tested both patches (this and previous). Both work.
>
> Also, please, add this for regzbot:
> > Fixes: 2d9223d2d64c ("ALSA: hda: Move controller drivers into sound/hda/controllers directory")
Actually this tag isn't really right. This commit casually surfaced
the issue in your particular case, but the bug itself was introduced
from the very beginning, and it could hit earlier.
thanks,
Takashi
next prev parent reply other threads:[~2025-12-10 13:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250709160434.1859-6-tiwai@suse.de>
2025-10-14 3:41 ` [REGRESSION][BISECTED] My audio broke (was: [PATCH 05/27] ALSA: hda: Move controller drivers into sound/hda/controllers directory) Askar Safin
2025-10-14 6:04 ` Takashi Iwai
2025-10-15 4:37 ` Askar Safin
2025-10-15 5:51 ` Takashi Iwai
2025-10-15 6:49 ` Askar Safin
2025-10-15 7:47 ` Takashi Iwai
2025-10-15 11:44 ` Askar Safin
2025-10-15 12:05 ` Takashi Iwai
2025-10-15 14:57 ` Askar Safin
2025-10-15 15:18 ` Takashi Iwai
2025-10-15 15:45 ` Askar Safin
2025-10-15 15:54 ` Takashi Iwai
2025-10-16 2:37 ` Askar Safin
2025-10-16 4:50 ` Askar Safin
2025-10-16 6:03 ` Askar Safin
2025-10-16 9:52 ` Takashi Iwai
2025-10-28 12:05 ` Takashi Iwai
2025-10-28 13:03 ` Askar Safin
2025-10-29 12:23 ` Askar Safin
2025-12-02 19:21 ` Askar Safin
2025-12-03 9:42 ` Takashi Iwai
2025-12-06 21:39 ` Askar Safin
2025-12-09 7:57 ` Takashi Iwai
2025-12-09 9:27 ` Takashi Iwai
2025-12-10 1:45 ` Askar Safin
2025-12-10 13:00 ` Takashi Iwai [this message]
2025-12-10 13:55 ` Thorsten Leemhuis
2025-12-11 18:11 ` Askar Safin
2025-10-15 15:02 ` Askar Safin
2025-10-15 5:01 ` Askar Safin
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=87345iebky.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Dell.Client.Kernel@dell.com \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=baojun.xu@ti.com \
--cc=bo.liu@senarytech.com \
--cc=cezary.rojewski@intel.com \
--cc=dxu@dxuuu.xyz \
--cc=kai.vehmanen@linux.intel.com \
--cc=kailang@realtek.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=ojeda@kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=regressions@lists.linux.dev \
--cc=rf@opensource.cirrus.com \
--cc=safinaskar@gmail.com \
--cc=sam@gentoo.org \
--cc=thomas.weissschuh@linutronix.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