From: Takashi Iwai <tiwai@suse.de>
To: Andy Chi <andy.chi@canonical.com>
Cc: "Jaroslav Kysela" <perex@perex.cz>,
"Takashi Iwai" <tiwai@suse.com>,
"Tim Crawford" <tcrawford@system76.com>,
"Stefan Binding" <sbinding@opensource.cirrus.com>,
"Meng Tang" <tangmeng@uniontech.com>,
"Philipp Jungkamp" <p.jungkamp@gmx.net>,
"Kacper Michajłow" <kasper93@gmail.com>,
"Gabriele Mazzotta" <gabriele.mzt@gmail.com>,
"Yuchi Yang" <yangyuchi66@gmail.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] ALSA: hda/realtek: Enable mute/micmute LEDs and speaker support for HP Laptops
Date: Tue, 14 Feb 2023 15:07:48 +0100 [thread overview]
Message-ID: <87edqs8hmz.wl-tiwai@suse.de> (raw)
In-Reply-To: <20230214140432.39654-1-andy.chi@canonical.com>
On Tue, 14 Feb 2023 15:04:31 +0100,
Andy Chi wrote:
>
> On HP Laptops, requires the ALC245_FIXUP_CS35L41_SPI_2_HP_GPIO_LED quirk to
> make its audio LEDs and speaker work.
>
> Signed-off-by: Andy Chi <andy.chi@canonical.com>
>
> v3: mentioned that this quirk also fix speaker in commit message
Thanks, applied.
Takashi
prev parent reply other threads:[~2023-02-14 14:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 3:58 [PATCH 1/2] ALSA: hda/realtek: fix mute/micmute LEDs don't work for a HP platform Andy Chi
2023-02-14 3:58 ` [PATCH 2/2] ALSA: hda/realtek: Enable mute/micmute LEDs support for HP Laptops Andy Chi
2023-02-14 10:24 ` Takashi Iwai
2023-02-14 10:25 ` [PATCH 1/2] ALSA: hda/realtek: fix mute/micmute LEDs don't work for a HP platform Takashi Iwai
2023-02-14 10:37 ` [PATCH v2] ALSA: hda/realtek: Enable mute/micmute LEDs support for HP Laptops Andy Chi
2023-02-14 11:27 ` Takashi Iwai
2023-02-14 14:04 ` [PATCH v3] ALSA: hda/realtek: Enable mute/micmute LEDs and speaker " Andy Chi
2023-02-14 14:07 ` 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=87edqs8hmz.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=andy.chi@canonical.com \
--cc=gabriele.mzt@gmail.com \
--cc=kasper93@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=p.jungkamp@gmx.net \
--cc=perex@perex.cz \
--cc=sbinding@opensource.cirrus.com \
--cc=tangmeng@uniontech.com \
--cc=tcrawford@system76.com \
--cc=tiwai@suse.com \
--cc=yangyuchi66@gmail.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