From: Sasha Levin <sashal@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Cristian Ciocaltea <cristian.ciocaltea@collabora.com>,
lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
lucas.tanure@collabora.com, pierre-louis.bossart@linux.intel.com,
rander.wang@intel.com, kuninori.morimoto.gx@renesas.com,
alsa-devel@alsa-project.org
Subject: Re: [PATCH AUTOSEL 6.4 04/31] ASoC: amd: vangogh: Use dmi_first_match() for DMI quirk handling
Date: Mon, 18 Sep 2023 17:29:49 -0400 [thread overview]
Message-ID: <ZQjBTUUJtY+1Q49X@sashalap> (raw)
In-Reply-To: <8d75077a-799a-4bf1-b259-a931c00fbc54@sirena.org.uk>
On Sat, Sep 09, 2023 at 12:20:16AM +0100, Mark Brown wrote:
>On Fri, Sep 08, 2023 at 03:31:33PM -0400, Sasha Levin wrote:
>> From: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
>>
>> [ Upstream commit 3dd26e27ccb4f18b4d25c0a49e1888eca9c6a724 ]
>>
>> In preparation for supporting ACPI probing, move DMI quirk handling
>> logic at the probe's top, to be able to return as quickly as possible in
>> case there is no DMI matching.
>
>As the changelog clearly says this is preparatory work for a new feature
>and therefore not stable material.
Dropped, thanks!
--
Thanks,
Sasha
next prev parent reply other threads:[~2023-09-18 21:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230908193201.3462957-1-sashal@kernel.org>
2023-09-08 19:31 ` [PATCH AUTOSEL 6.4 04/31] ASoC: amd: vangogh: Use dmi_first_match() for DMI quirk handling Sasha Levin
2023-09-08 23:20 ` Mark Brown
2023-09-18 21:29 ` Sasha Levin [this message]
2023-09-08 19:31 ` [PATCH AUTOSEL 6.4 15/31] ASoC: SOF: topology: simplify code to prevent static analysis warnings Sasha Levin
2023-09-08 19:31 ` [PATCH AUTOSEL 6.4 16/31] ASoC: Intel: sof_sdw: Update BT offload config for soundwire config Sasha Levin
2023-09-08 19:31 ` [PATCH AUTOSEL 6.4 17/31] ALSA: hda: intel-dsp-cfg: add LunarLake support Sasha Levin
2023-09-08 19:31 ` [PATCH AUTOSEL 6.4 30/31] ASoC: SOF: amd: clear panic mask status when panic occurs 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=ZQjBTUUJtY+1Q49X@sashalap \
--to=sashal@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cristian.ciocaltea@collabora.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.tanure@collabora.com \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rander.wang@intel.com \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.com \
/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