From: Sasha Levin <sashal@kernel.org>
To: Askar Safin <safinaskar@gmail.com>
Cc: patches@lists.linux.dev, stable@vger.kernel.org,
Takashi Iwai <tiwai@suse.de>,
Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
kai.vehmanen@linux.intel.com, cezary.rojewski@intel.com,
ranjani.sridharan@linux.intel.com, rf@opensource.cirrus.com,
bradynorander@gmail.com
Subject: Re: [PATCH AUTOSEL 6.18-6.17] ALSA: hda: intel-dsp-config: Prefer legacy driver as fallback
Date: Wed, 7 Jan 2026 06:16:55 -0500 [thread overview]
Message-ID: <aV5Ap8TgMEDLucWR@laps> (raw)
In-Reply-To: <CAPnZJGD0ifVdHTRcMzKBFX8UEf_me1KTrkbwezZrhzndcTx-3Q@mail.gmail.com>
On Tue, Dec 16, 2025 at 02:29:14AM +0300, Askar Safin wrote:
>On Mon, Dec 15, 2025 at 3:41 AM Sasha Levin <sashal@kernel.org> wrote:
>>
>> From: Takashi Iwai <tiwai@suse.de>
>>
>> [ Upstream commit 161a0c617ab172bbcda7ce61803addeb2124dbff ]
>>
>> When config table entries don't match with the device to be probed,
>> currently we fall back to SND_INTEL_DSP_DRIVER_ANY, which means to
>> allow any drivers to bind with it.
>>
>[...]
>>
>> Reported-by: Askar Safin <safinaskar@gmail.com>
>> Closes: https://lore.kernel.org/all/20251014034156.4480-1-safinaskar@gmail.com/
>> Tested-by: Askar Safin <safinaskar@gmail.com>
>> Reviewed-by: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
>> Signed-off-by: Takashi Iwai <tiwai@suse.de>
>> Link: https://patch.msgid.link/20251210131553.184404-1-tiwai@suse.de
>> Signed-off-by: Sasha Levin <sashal@kernel.org>
>> ---
>
>Please, backport this to 82d9d54a6c0e .
>82d9d54a6c0e is commit, which introduced "intel-dsp-config.c".
Looks like that commit is already in all trees.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-01-07 11:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 0:41 [PATCH AUTOSEL 6.18-6.17] ALSA: hda/realtek: Add support for ASUS UM3406GA Sasha Levin
2025-12-15 0:41 ` [PATCH AUTOSEL 6.18-6.1] smb/client: fix NT_STATUS_NO_DATA_DETECTED value Sasha Levin
2025-12-15 0:41 ` [PATCH AUTOSEL 6.18-6.17] ALSA: hda: intel-dsp-config: Prefer legacy driver as fallback Sasha Levin
2025-12-15 23:29 ` Askar Safin
2026-01-07 11:16 ` Sasha Levin [this message]
2026-01-11 12:04 ` Askar Safin
2026-01-11 12:24 ` Greg KH
2026-01-11 16:01 ` Askar Safin
2026-01-12 10:54 ` Greg KH
2026-01-15 14:34 ` [PATCH 6.12.y] " Askar Safin
2026-01-15 14:40 ` [PATCH AUTOSEL 6.18-6.17] " Askar Safin
2025-12-15 0:41 ` [PATCH AUTOSEL 6.18-6.12] ASoC: rockchip: Fix Wvoid-pointer-to-enum-cast warning (again) Sasha Levin
2025-12-15 0:41 ` [PATCH AUTOSEL 6.18-5.10] NFSv4: ensure the open stateid seqid doesn't go backwards Sasha Levin
2025-12-15 0:41 ` [PATCH AUTOSEL 6.18-6.1] bcache: fix improper use of bi_end_io Sasha Levin
2025-12-15 0:41 ` [PATCH AUTOSEL 6.18-5.10] NFS: Fix up the automount fs_context to use the correct cred Sasha Levin
2025-12-15 0:41 ` [PATCH AUTOSEL 6.18-6.1] smb/client: fix NT_STATUS_DEVICE_DOOR_OPEN value Sasha Levin
2025-12-15 0:41 ` [PATCH AUTOSEL 6.18-6.1] smb/client: fix NT_STATUS_UNABLE_TO_FREE_VM value Sasha Levin
2025-12-15 0:41 ` [PATCH AUTOSEL 6.18-6.12] drm/amd/display: shrink struct members Sasha Levin
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=aV5Ap8TgMEDLucWR@laps \
--to=sashal@kernel.org \
--cc=bradynorander@gmail.com \
--cc=cezary.rojewski@intel.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=patches@lists.linux.dev \
--cc=peter.ujfalusi@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=rf@opensource.cirrus.com \
--cc=safinaskar@gmail.com \
--cc=stable@vger.kernel.org \
--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