From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Hui Wang <hui.wang@canonical.com>
To: alsa-devel@alsa-project.org, tiwai@suse.de, stable@vger.kernel.org
Cc: Kailang Yang <kailang@realtek.com>, stable@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/realtek - a fake key event is triggered by running shutup
Date: Tue, 31 Mar 2020 13:11:29 +0000 [thread overview]
Message-ID: <20200331131130.0A72620757@mail.kernel.org> (raw)
In-Reply-To: <20200329080642.20287-1-hui.wang@canonical.com>
Hi
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag
fixing commit: 78def224f59c ("ALSA: hda/realtek - Add Headset Mic supported").
The bot has tested the following trees: v5.5.13, v5.4.28, v4.19.113.
v5.5.13: Build OK!
v5.4.28: Build OK!
v4.19.113: Failed to apply! Possible dependencies:
10f5b1b85ed1 ("ALSA: hda/realtek - Fixed Headset Mic JD not stable")
2b3b6497c38d ("ALSA: hda/realtek - Add more codec supported Headset Button")
8983eb602af5 ("ALSA: hda/realtek - Move to ACT_INIT state")
c8a9afa632f0 ("ALSA: hda/realtek: merge alc_fixup_headset_jack to alc295_fixup_chromebook")
d3ba58bb8959 ("ALSA: hda/realtek - Support low power consumption for ALC295")
e854747d7593 ("ALSA: hda/realtek - Enable headset button support for new codec")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Hui Wang <hui.wang@canonical.com>
To: alsa-devel@alsa-project.org, tiwai@suse.de, stable@vger.kernel.org
Cc: Kailang Yang <kailang@realtek.com>
Cc: <stable@vger.kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/realtek - a fake key event is triggered by running shutup
Date: Tue, 31 Mar 2020 13:11:29 +0000 [thread overview]
Message-ID: <20200331131130.0A72620757@mail.kernel.org> (raw)
In-Reply-To: <20200329080642.20287-1-hui.wang@canonical.com>
Hi
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag
fixing commit: 78def224f59c ("ALSA: hda/realtek - Add Headset Mic supported").
The bot has tested the following trees: v5.5.13, v5.4.28, v4.19.113.
v5.5.13: Build OK!
v5.4.28: Build OK!
v4.19.113: Failed to apply! Possible dependencies:
10f5b1b85ed1 ("ALSA: hda/realtek - Fixed Headset Mic JD not stable")
2b3b6497c38d ("ALSA: hda/realtek - Add more codec supported Headset Button")
8983eb602af5 ("ALSA: hda/realtek - Move to ACT_INIT state")
c8a9afa632f0 ("ALSA: hda/realtek: merge alc_fixup_headset_jack to alc295_fixup_chromebook")
d3ba58bb8959 ("ALSA: hda/realtek - Support low power consumption for ALC295")
e854747d7593 ("ALSA: hda/realtek - Enable headset button support for new codec")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
next prev parent reply other threads:[~2020-03-31 13:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 8:06 [PATCH] ALSA: hda/realtek - a fake key event is triggered by running shutup Hui Wang
2020-03-29 8:17 ` Hui Wang
2020-03-31 13:11 ` Sasha Levin [this message]
2020-03-31 13:11 ` Sasha Levin
2020-03-31 13:18 ` Hui Wang
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=20200331131130.0A72620757@mail.kernel.org \
--to=sashal@kernel.org \
--cc=kailang@realtek.com \
--cc=stable@vger.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 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.