From: Michael Diesen <michael.diesen@posteo.de>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, Takashi Iwai <tiwai@suse.de>,
linux-sound@vger.kernel.org
Subject: Re: Please apply bed0c8084044 to 7.1.y and 6.18.y
Date: Mon, 17 Aug 2026 08:58:48 +0000 [thread overview]
Message-ID: <1786957127.718071.28963@posteo.de> (raw)
In-Reply-To: <20260801154223.stable-0005@kernel.org>
On Sat, Aug 01, 2026 at 06:13:27PM -0400, Sasha Levin wrote:
> Queued for 7.1 and 6.18, thanks.
>
> 6.18 was missing the earlier 103c:8a06 Dragonfly Folio quirk that this
> entry sorts next to, so that one went in ahead of it.
Thanks - 7.1.y picked it up in 7.1.8.
For 6.18.y the prerequisite is in place now: 302eb8765132 ("ALSA:
hda/realtek: add quirk for HP Dragonfly Folio G3 2-in-1") went in with
6.18.44. The 8a05 entry itself does not appear to have followed it,
though - linux-6.18.y still carries only the 8a06 line in
sound/hda/codecs/realtek/alc269.c, and I do not see it in queue/6.18
either.
Could you queue bed0c8084044 ("ALSA: hda/realtek: Add quirk for HP
Dragonfly Folio G3 2-in-1 (103c:8a05)") for 6.18.y as well?
One note in case it is applied as a plain patch: the last context line
of the hunk is the 103c:8a1b entry, which 6.18 does not have, so git am
needs -3 there. The change itself is a single quirk table line directly
above the 8a06 entry.
Thanks,
Michael
next prev parent reply other threads:[~2026-08-17 8:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 20:50 Please apply bed0c8084044 to 7.1.y and 6.18.y Michael Diesen
2026-08-01 22:13 ` Sasha Levin
2026-08-17 8:58 ` Michael Diesen [this message]
2026-08-17 15:24 ` Sasha Levin
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=1786957127.718071.28963@posteo.de \
--to=michael.diesen@posteo.de \
--cc=linux-sound@vger.kernel.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 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.