From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: aik@ozlabs.ru, paulus@ozlabs.org, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] KVM: PPC: Book3S: Fix incorrect guest-to-user-translation" failed to apply to 4.19-stable tree
Date: Tue, 3 Sep 2019 16:21:13 -0400 [thread overview]
Message-ID: <20190903202113.GK5281@sasha-vm> (raw)
In-Reply-To: <156753601315657@kroah.com>
On Tue, Sep 03, 2019 at 08:40:13PM +0200, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 4.19-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>.
I've fixed it up for 4.19 and 4.14. The issue was mostly due to missing
2001825efcea7 ("KVM: PPC: Book3S HV: Avoid lockdep debugging in TCE
realmode handlers").
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-09-03 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 18:40 FAILED: patch "[PATCH] KVM: PPC: Book3S: Fix incorrect guest-to-user-translation" failed to apply to 4.19-stable tree gregkh
2019-09-03 20:21 ` Sasha Levin [this message]
2019-09-04 5:26 ` Greg KH
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=20190903202113.GK5281@sasha-vm \
--to=sashal@kernel.org \
--cc=aik@ozlabs.ru \
--cc=gregkh@linuxfoundation.org \
--cc=paulus@ozlabs.org \
--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 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).