From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: stable <stable@vger.kernel.org>, Sasha Levin <sashal@kernel.org>,
Takashi Iwai <tiwai@suse.de>
Subject: Re: Please apply commit 8983dc1b66c0 ("ALSA: hda/realtek: Fix built-in mic on another ASUS VivoBook model") to v6.1.y (and v6.6.y)
Date: Thu, 24 Apr 2025 17:31:14 +0200 [thread overview]
Message-ID: <2025042459-debit-slicing-84e2@gregkh> (raw)
In-Reply-To: <aApNxe237XfXGLS-@eldamar.lan>
On Thu, Apr 24, 2025 at 04:42:13PM +0200, Salvatore Bonaccorso wrote:
> Hi
>
> As per subject, can you please apply commit 8983dc1b66c0 ("ALSA:
> hda/realtek: Fix built-in mic on another ASUS VivoBook model") to
> v6.1.y?
>
> The commit fixes 3b4309546b48 ("ALSA: hda: Fix headset detection
> failure due to unstable sort"), which is in 6.14-rc1 *but* it got
> backported to other stable series as well: 6.1.129, 6.6.78, 6.12.14
> and 6.13.3.
>
> While 8983dc1b66c0 got then backported down to 6.12.23, 6.13.11 and
> and 6.14.2 it was not backported further down, the reason is likely
> the commit does not apply cleanly due to context changes in the struct
> hda_quirk alc269_fixup_tbl (as some entries are missing in older
> series).
>
> For context see as well:
> https://lore.kernel.org/linux-sound/Z95s5T6OXFPjRnKf@eldamar.lan
> https://lore.kernel.org/linux-sound/Z_aq9kkdswrGZRUQ@eldamar.lan/
> https://bugs.debian.org/1100928
>
> Can you please apply it down for 6.1.y?
>
> Attached is a manual backport of the change in case needed.
The backport was needed and was why this wasn't applied there, thanks!
greg k-h
prev parent reply other threads:[~2025-04-24 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 14:42 Please apply commit 8983dc1b66c0 ("ALSA: hda/realtek: Fix built-in mic on another ASUS VivoBook model") to v6.1.y (and v6.6.y) Salvatore Bonaccorso
2025-04-24 15:31 ` Greg Kroah-Hartman [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=2025042459-debit-slicing-84e2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=carnil@debian.org \
--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