From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Thomas Hebb <tommyhebb@gmail.com>
To: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Cc: Kailang Yang <kailang@realtek.com>
Cc: stable@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 3/3] ALSA: hda/realtek - Remove now-unnecessary XPS 13 headphone noise fixups
Date: Tue, 31 Mar 2020 13:11:30 +0000 [thread overview]
Message-ID: <20200331131131.2A2BE21924@mail.kernel.org> (raw)
In-Reply-To: <028b0c410238090546cf80ef6075b3b9139986a7.1585553414.git.tommyhebb@gmail.com>
Hi
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag
fixing commit: 8c69729b4439 ("ALSA: hda - Fix headphone noise after Dell XPS 13 resume back from S3").
The bot has tested the following trees: v5.5.13, v5.4.28, v4.19.113, v4.14.174, v4.9.217, v4.4.217.
v5.5.13: Build OK!
v5.4.28: Build OK!
v4.19.113: Build OK!
v4.14.174: Failed to apply! Possible dependencies:
1099f48457d0 ("ALSA: hda/realtek: Reduce the Headphone static noise on XPS 9350/9360")
28d1d6d2f314 ("ALSA: hda - Add model string for Intel reference board quirk")
a26d96c7802e ("ALSA: hda/realtek - Comprehensive model list for ALC259 & co")
c0ca5eced222 ("ALSA: hda/realtek - Reduce click noise on Dell Precision 5820 headphone")
c1350bff69d1 ("ALSA: hda - Clean up ALC299 init code")
da911b1f5e98 ("ALSA: hda/realtek - update ALC225 depop optimize")
v4.9.217: Failed to apply! Possible dependencies:
8551914a5e19 ("ALSA: doc: ReSTize alsa-driver-api document")
9000d69925ac ("ALSA: doc: ReSTize HD-Audio document")
a26d96c7802e ("ALSA: hda/realtek - Comprehensive model list for ALC259 & co")
a4caad753f0c ("ALSA: doc: ReSTize HD-Audio-Models document")
a79e7df97592 ("ALSA: hda - Update the list of quirk models")
v4.4.217: Failed to apply! Possible dependencies:
34d505193bd1 ("cfg80211: basic support for PBSS network type")
35eb8f7b1a37 ("cfg80211: Improve Connect/Associate command documentation")
38de03d2a289 ("nl80211: add feature for BSS selection support")
819bf593767c ("docs-rst: sphinxify 802.11 documentation")
8551914a5e19 ("ALSA: doc: ReSTize alsa-driver-api document")
9000d69925ac ("ALSA: doc: ReSTize HD-Audio document")
a26d96c7802e ("ALSA: hda/realtek - Comprehensive model list for ALC259 & co")
a4caad753f0c ("ALSA: doc: ReSTize HD-Audio-Models document")
ba6fbacf9c07 ("cfg80211: Add option to specify previous BSSID for Connect command")
bf1ecd210541 ("cfg80211: Allow cfg80211_connect_result() errors to be distinguished")
e705498945ad ("cfg80211: Add option to report the bss entry in connect result")
fa44b7ec9bc4 ("ALSA: hda - Update documentation")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
prev parent reply other threads:[~2020-03-31 13:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1585553414.git.tommyhebb@gmail.com>
2020-03-30 7:30 ` [PATCH 1/3] ALSA: doc: Document PC Beep Hidden Register on Realtek ALC256 Thomas Hebb
2020-03-31 13:11 ` Sasha Levin
2020-03-30 7:30 ` [PATCH 2/3] ALSA: hda/realtek - Set principled PC Beep configuration for ALC256 Thomas Hebb
2020-03-30 7:30 ` [PATCH 3/3] ALSA: hda/realtek - Remove now-unnecessary XPS 13 headphone noise fixups Thomas Hebb
2020-03-31 13:11 ` 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=20200331131131.2A2BE21924@mail.kernel.org \
--to=sashal@kernel.org \
--cc=kailang@realtek.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;
as well as URLs for NNTP newsgroup(s).