From: Greg KH <gregkh@linuxfoundation.org>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, Chris Chiu <chris.chiu@canonical.com>,
Takashi Iwai <tiwai@suse.de>
Subject: Re: [PATCH 6.6.y] ALSA: hda/realtek - Add new HP ZBook laptop with micmute led fixup
Date: Sun, 7 Sep 2025 09:54:46 +0200 [thread overview]
Message-ID: <2025090758-chasing-cassette-aa76@gregkh> (raw)
In-Reply-To: <20250905211700.3421432-1-sashal@kernel.org>
On Fri, Sep 05, 2025 at 05:17:00PM -0400, Sasha Levin wrote:
> From: Chris Chiu <chris.chiu@canonical.com>
>
> [ Upstream commit f709b78aecab519dbcefa9a6603b94ad18c553e3 ]
>
> New HP ZBook with Realtek HDA codec ALC3247 needs the quirk
> ALC236_FIXUP_HP_GPIO_LED to fix the micmute LED.
>
> Signed-off-by: Chris Chiu <chris.chiu@canonical.com>
> Cc: <stable@vger.kernel.org>
> Link: https://patch.msgid.link/20250520132101.120685-1-chris.chiu@canonical.com
> Signed-off-by: Takashi Iwai <tiwai@suse.de>
> [ Adjust context ]
> Signed-off-by: Sasha Levin <sashal@kernel.org>
> ---
> sound/pci/hda/patch_realtek.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
> index d4bc80780a1f9..b47820105ead4 100644
> --- a/sound/pci/hda/patch_realtek.c
> +++ b/sound/pci/hda/patch_realtek.c
> @@ -10249,6 +10249,7 @@ static const struct hda_quirk alc269_fixup_tbl[] = {
> SND_PCI_QUIRK(0x103c, 0x8e18, "HP ZBook Firefly 14 G12A", ALC285_FIXUP_HP_GPIO_LED),
> SND_PCI_QUIRK(0x103c, 0x8e19, "HP ZBook Firefly 14 G12A", ALC285_FIXUP_HP_GPIO_LED),
> SND_PCI_QUIRK(0x103c, 0x8e1a, "HP ZBook Firefly 14 G12A", ALC285_FIXUP_HP_GPIO_LED),
> + SND_PCI_QUIRK(0x103c, 0x8e1d, "HP ZBook X Gli 16 G12", ALC236_FIXUP_HP_GPIO_LED),
> SND_PCI_QUIRK(0x1043, 0x103e, "ASUS X540SA", ALC256_FIXUP_ASUS_MIC),
> SND_PCI_QUIRK(0x1043, 0x103f, "ASUS TX300", ALC282_FIXUP_ASUS_TX300),
> SND_PCI_QUIRK(0x1043, 0x1054, "ASUS G614FH/FM/FP", ALC287_FIXUP_CS35L41_I2C_2),
> --
> 2.50.1
>
>
This, and the other alsa patch for 6.6, conflicted as you only
backported these on a "clean" tree. I've fixed it up by hand, but I
don't know if you have a way to determine that these are in a "series"
or not.
thanks,
greg k-h
prev parent reply other threads:[~2025-09-07 7:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-24 15:47 FAILED: patch "[PATCH] ALSA: hda/realtek - Add new HP ZBook laptop with micmute led" failed to apply to 6.6-stable tree gregkh
2025-09-05 21:17 ` [PATCH 6.6.y] ALSA: hda/realtek - Add new HP ZBook laptop with micmute led fixup Sasha Levin
2025-09-07 7:54 ` Greg KH [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=2025090758-chasing-cassette-aa76@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=chris.chiu@canonical.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--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