From: Sasha Levin <sashal@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Takashi Iwai <tiwai@suse.de>,
kailang@realtek.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] ALSA: hda/realtek - Add Bass Speaker and fixed dac for bass" failed to apply to 5.4-stable tree
Date: Tue, 7 Jan 2020 13:59:56 -0500 [thread overview]
Message-ID: <20200107185956.GC1706@sasha-vm> (raw)
In-Reply-To: <20200107093912.GA1031189@kroah.com>
On Tue, Jan 07, 2020 at 10:39:12AM +0100, Greg KH wrote:
>On Mon, Jan 06, 2020 at 09:32:43PM +0100, Takashi Iwai wrote:
>> On Mon, 06 Jan 2020 13:10:30 +0100,
>> <gregkh@linuxfoundation.org> wrote:
>> >
>> >
>> > The patch below does not apply to the 5.4-stable tree.
>> > If someone wants it applied there, or to any other stable or longterm
>> > tree, then please email the backport, including the original git commit
>> > id to <stable@vger.kernel.org>.
>>
>> Hm, I could cherry-pick the commit e79c22695abd (also commit
>> 48e01504cf53 at next) cleanly on linux-5.4.y branch.
>>
>> Could you try again?
>
>Ugh, my fault, seems Sasha already queued these patches up in the stable
>tree and I didn't notice them. When I tried to apply them they
>rightfully complained :(
>
>sorry for the noise, all is good here.
Appologies for stepping on your toes here, I picked it up so that I
could also take 48e01504cf53 ("ALSA: hda/realtek - Enable the bass
speaker of ASUS UX431FLC") which fixes a different patch we took in the
5.4 tree.
--
Thanks,
Sasha
prev parent reply other threads:[~2020-01-07 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 12:10 FAILED: patch "[PATCH] ALSA: hda/realtek - Add Bass Speaker and fixed dac for bass" failed to apply to 5.4-stable tree gregkh
2020-01-06 20:32 ` Takashi Iwai
2020-01-07 9:39 ` Greg KH
2020-01-07 18:59 ` 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=20200107185956.GC1706@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kailang@realtek.com \
--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;
as well as URLs for NNTP newsgroup(s).