Linux kbuild/kconfig development
 help / color / mirror / Atom feed
From: Askar Safin <safinaskar@gmail.com>
To: tiwai@suse.de
Cc: Dell.Client.Kernel@dell.com, amadeuszx.slawinski@linux.intel.com,
	baojun.xu@ti.com, bo.liu@senarytech.com,
	cezary.rojewski@intel.com, dxu@dxuuu.xyz,
	kai.vehmanen@linux.intel.com, kailang@realtek.com,
	linux-kbuild@vger.kernel.org, linux-sound@vger.kernel.org,
	masahiroy@kernel.org, miguel.ojeda.sandonis@gmail.com,
	nathan@kernel.org, nsc@kernel.org, ojeda@kernel.org,
	patches@opensource.cirrus.com, regressions@lists.linux.dev,
	rf@opensource.cirrus.com, safinaskar@gmail.com, sam@gentoo.org,
	thomas.weissschuh@linutronix.de
Subject: Re: [REGRESSION][BISECTED] My audio broke (was: [PATCH 05/27] ALSA: hda: Move controller drivers into sound/hda/controllers directory)
Date: Wed, 29 Oct 2025 15:23:21 +0300	[thread overview]
Message-ID: <20251029122321.2872-1-safinaskar@gmail.com> (raw)
In-Reply-To: <878qgvgrk0.wl-tiwai@suse.de>

I just noticed (when debugging unrelated bug) another thing: whether audio
works depends on what initramfs
generator I use. "initramfs-tools" vs hand-written one. So it seems that
set of modules loaded by initramfs affects whether audio works.

-- 
Askar Safin

  parent reply	other threads:[~2025-10-29 12:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87o6q8l68r.wl-tiwai@suse.de>
     [not found] ` <20251015145749.2572-1-safinaskar@gmail.com>
     [not found]   ` <878qhckxc5.wl-tiwai@suse.de>
     [not found]     ` <CAPnZJGDeCkqqUpEh0SBfwvsxfMp9ZDXqvhrC1s9zRp6jX+Fvnw@mail.gmail.com>
     [not found]       ` <875xcgkvnw.wl-tiwai@suse.de>
     [not found]         ` <CAPnZJGDmCnKPz2eygwDjQGXZWVctGyJxV+OeFSLLeZPOCEvvbA@mail.gmail.com>
2025-10-16  4:50           ` [REGRESSION][BISECTED] My audio broke (was: [PATCH 05/27] ALSA: hda: Move controller drivers into sound/hda/controllers directory) 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 [this message]
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
2025-12-10 13:55                               ` Thorsten Leemhuis
2025-12-11 18:11                               ` 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=20251029122321.2872-1-safinaskar@gmail.com \
    --to=safinaskar@gmail.com \
    --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=sam@gentoo.org \
    --cc=thomas.weissschuh@linutronix.de \
    --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