From: Sasha Levin <sashal@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Simon Trimmer <simont@opensource.cirrus.com>,
perex@perex.cz, tiwai@suse.com, rf@opensource.cirrus.com,
broonie@kernel.org, shenghao-ding@ti.com,
sbinding@opensource.cirrus.com, lukas.bulwahn@gmail.com,
linux-sound@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 6.6 11/12] ALSA: hda: cs35l56: Select SERIAL_MULTI_INSTANTIATE
Date: Mon, 22 Jul 2024 08:50:40 -0400 [thread overview]
Message-ID: <Zp5VoMzMjH6gHExm@sashalap> (raw)
In-Reply-To: <87wmm5a8ka.wl-tiwai@suse.de>
On Mon, Jul 01, 2024 at 09:13:41AM +0200, Takashi Iwai wrote:
>On Mon, 01 Jul 2024 02:13:30 +0200,
>Sasha Levin wrote:
>>
>> From: Simon Trimmer <simont@opensource.cirrus.com>
>>
>> [ Upstream commit 9b1effff19cdf2230d3ecb07ff4038a0da32e9cc ]
>>
>> The ACPI IDs used in the CS35L56 HDA drivers are all handled by the
>> serial multi-instantiate driver which starts multiple Linux device
>> instances from a single ACPI Device() node.
>>
>> As serial multi-instantiate is not an optional part of the system add it
>> as a dependency in Kconfig so that it is not overlooked.
>>
>> Signed-off-by: Simon Trimmer <simont@opensource.cirrus.com>
>> Link: https://lore.kernel.org/20240619161602.117452-1-simont@opensource.cirrus.com
>> Signed-off-by: Takashi Iwai <tiwai@suse.de>
>> Signed-off-by: Sasha Levin <sashal@kernel.org>
>
>This change breaks random builds, so please pick up a follow-up fix
>17563b4a19d1844bdbccc7a82d2f31c28ca9cfae
> ALSA: hda: Use imply for suggesting CONFIG_SERIAL_MULTI_INSTANTIATE
>too.
Will do.
--
Thanks,
Sasha
next prev parent reply other threads:[~2024-07-22 12:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 0:13 [PATCH AUTOSEL 6.6 01/12] ALSA: hda: cs35l56: Fix lifecycle of codec pointer Sasha Levin
2024-07-01 0:13 ` [PATCH AUTOSEL 6.6 02/12] wifi: cfg80211: wext: add extra SIOCSIWSCAN data check Sasha Levin
2024-07-01 0:13 ` [PATCH AUTOSEL 6.6 03/12] ALSA: hda/realtek: Support Lenovo Thinkbook 16P Gen 5 Sasha Levin
2024-07-01 0:13 ` [PATCH AUTOSEL 6.6 04/12] KVM: PPC: Book3S HV: Prevent UAF in kvm_spapr_tce_attach_iommu_group() Sasha Levin
2024-07-01 0:13 ` [PATCH AUTOSEL 6.6 05/12] drm/vmwgfx: Fix missing HYPERVISOR_GUEST dependency Sasha Levin
2024-07-01 0:13 ` [PATCH AUTOSEL 6.6 06/12] ALSA: hda/realtek: Add more codec ID to no shutup pins list Sasha Levin
2024-07-01 0:13 ` [PATCH AUTOSEL 6.6 07/12] spi: Fix OCTAL mode support Sasha Levin
2024-07-01 0:13 ` [PATCH AUTOSEL 6.6 08/12] cpumask: limit FORCE_NR_CPUS to just the UP case Sasha Levin
2024-07-01 0:13 ` [PATCH AUTOSEL 6.6 09/12] selftests: openvswitch: Set value to nla flags Sasha Levin
2024-07-01 0:13 ` [PATCH AUTOSEL 6.6 10/12] drm/amdgpu: Indicate CU havest info to CP Sasha Levin
2024-07-01 0:13 ` [PATCH AUTOSEL 6.6 11/12] ALSA: hda: cs35l56: Select SERIAL_MULTI_INSTANTIATE Sasha Levin
2024-07-01 7:13 ` Takashi Iwai
2024-07-22 12:50 ` Sasha Levin [this message]
2024-07-01 0:13 ` [PATCH AUTOSEL 6.6 12/12] mips: fix compat_sys_lseek syscall 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=Zp5VoMzMjH6gHExm@sashalap \
--to=sashal@kernel.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=perex@perex.cz \
--cc=rf@opensource.cirrus.com \
--cc=sbinding@opensource.cirrus.com \
--cc=shenghao-ding@ti.com \
--cc=simont@opensource.cirrus.com \
--cc=stable@vger.kernel.org \
--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