From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Vinod Koul <vkoul@kernel.org>,
linux-sound@vger.kernel.org, Sergey Lebedev <lsa.uz@pm.me>
Subject: Re: [STABLE REQUEST] soundwire: dmi-quirks: drop the ghost RT1320 on the Surface Pro 11 (Intel)
Date: Thu, 19 Nov 2026 11:08:26 -0500 [thread overview]
Message-ID: <2026-11-19-1-daily-reply-0024@kernel.org> (raw)
In-Reply-To: <20261119064745.65211-1-lsa.uz@pm.me>
> Please consider for 7.3.y and 6.18.y:
>
> d32e04c05234 ("soundwire: dmi-quirks: drop the ghost RT1320 on the Surface Pro 11 (Intel)")
Queued for 7.3 and 6.18, thanks. It needed the two Lenovo quirk entries before
it in the table, so those went in with it.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-11-19 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 6:47 [STABLE REQUEST] soundwire: dmi-quirks: drop the ghost RT1320 on the Surface Pro 11 (Intel) Sergey Lebedev
2026-11-19 16:08 ` Sasha Levin [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=2026-11-19-1-daily-reply-0024@kernel.org \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-sound@vger.kernel.org \
--cc=lsa.uz@pm.me \
--cc=stable@vger.kernel.org \
--cc=vkoul@kernel.org \
/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