From: Takashi Iwai <tiwai@suse.de>
To: Mark Hasemeyer <markhas@chromium.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Guenter Roeck" <linux@roeck-us.net>,
stable@vger.kernel.org,
"Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Bard Liao" <yung-chuan.liao@linux.intel.com>,
"Brady Norander" <bradynorander@gmail.com>,
"Jaroslav Kysela" <perex@perex.cz>,
"Mark Brown" <broonie@kernel.org>,
"Pierre-Louis Bossart" <pierre-louis.bossart@linux.intel.com>,
"Takashi Iwai" <tiwai@suse.com>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH v1] ALSA: hda: intel-dsp-config: Fix JSL Chromebook quirk detection
Date: Fri, 20 Oct 2023 17:40:14 +0200 [thread overview]
Message-ID: <87r0lpi9pd.wl-tiwai@suse.de> (raw)
In-Reply-To: <20231018235944.1860717-1-markhas@chromium.org>
On Thu, 19 Oct 2023 01:59:31 +0200,
Mark Hasemeyer wrote:
>
> Some Jasperlake Chromebooks overwrite the system vendor DMI value to the
> name of the OEM that manufactured the device. This breaks Chromebook
> quirk detection as it expects the system vendor to be "Google".
>
> Add another quirk detection entry that looks for "Google" in the BIOS
> version.
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Mark Hasemeyer <markhas@chromium.org>
Applied now. Thanks.
Takashi
prev parent reply other threads:[~2023-10-20 15:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 23:59 [PATCH v1] ALSA: hda: intel-dsp-config: Fix JSL Chromebook quirk detection Mark Hasemeyer
2023-10-19 14:22 ` Amadeusz Sławiński
2023-10-19 16:43 ` Mark Hasemeyer
2023-10-19 17:00 ` Pierre-Louis Bossart
2023-10-20 15:36 ` Mark Hasemeyer
2023-10-20 16:59 ` Pierre-Louis Bossart
2023-10-20 18:36 ` Curtis Malainey
2023-10-20 19:35 ` Mark Hasemeyer
2023-10-20 15:40 ` Takashi Iwai [this message]
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=87r0lpi9pd.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bradynorander@gmail.com \
--cc=broonie@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=markhas@chromium.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.com \
--cc=yung-chuan.liao@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.