From: Sven Frotscher <sven.frotscher@gmail.com>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
Mark Brown <broonie@kernel.org>,
git@augustwikerfors.se, alsa-devel@alsa-project.org,
lgirdwood@gmail.com, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, Takashi Iwai <tiwai@suse.com>
Subject: Re: [PATCH v4] ASoC: amd: yc: Fix non-functional mic on Lenovo 82YM
Date: Mon, 02 Oct 2023 16:40:47 +0200 [thread overview]
Message-ID: <0SOW1S.YTFHPA95XPTN@gmail.com> (raw)
In-Reply-To: <28e38593-4861-4d61-b27d-994328ea4e82@amd.com>
Am Mo, 2. Okt 2023 um 09:20:04 -05:00:00 schrieb Mario Limonciello
<mario.limonciello@amd.com>:
> I'm not positive, but the only way we get a full list is from Lenovo.
In order to be totally certain, yes.
But maybe the non-quirk check can be expanded to also cover (some of)
the affected Lenovo models. As I said, I'm open to provide some
relevant info from mine if someone tells me what "relevant info" means
in this case.
next prev parent reply other threads:[~2023-10-02 14:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 22:36 [PATCH v4] ASoC: amd: yc: Fix non-functional mic on Lenovo 82YM Sven Frotscher
2023-10-02 9:32 ` Linux regression tracking (Thorsten Leemhuis)
2023-10-02 11:52 ` Mark Brown
2023-10-02 12:28 ` Linux regression tracking (Thorsten Leemhuis)
2023-10-02 12:54 ` Mark Brown
2023-10-02 13:00 ` Sven Frotscher
2023-10-02 13:04 ` Mark Brown
2023-10-02 13:17 ` Sven Frotscher
2023-10-02 13:47 ` Mark Brown
2023-10-02 13:47 ` Mario Limonciello
2023-10-02 14:13 ` Linux regression tracking (Thorsten Leemhuis)
2023-10-02 14:20 ` Mario Limonciello
2023-10-02 14:36 ` Linux regression tracking (Thorsten Leemhuis)
2023-10-02 14:40 ` Sven Frotscher [this message]
2023-10-02 18:51 ` Mark Brown
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=0SOW1S.YTFHPA95XPTN@gmail.com \
--to=sven.frotscher@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=git@augustwikerfors.se \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=regressions@lists.linux.dev \
--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