From: Greg KH <gregkh@linuxfoundation.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: lprosek@redhat.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] KVM: nVMX: update last_nonleaf_level when initializing nested" failed to apply to 4.4-stable tree
Date: Mon, 16 Oct 2017 18:13:30 +0200 [thread overview]
Message-ID: <20171016161330.GB30572@kroah.com> (raw)
In-Reply-To: <eab9853d-6455-7fd4-fd09-6a4117701997@redhat.com>
On Mon, Oct 16, 2017 at 06:06:43PM +0200, Paolo Bonzini wrote:
> On 16/10/2017 18:03, gregkh@linuxfoundation.org wrote:
> > The patch below does not apply to the 4.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>.
>
> It's okay not to apply the patch; the bug was only latent before 4.6.
That's not what the patch itself said :)
Anyway, thanks for the quick response, I'll leave this alone for 4.4.
greg k-h
prev parent reply other threads:[~2017-10-16 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 16:03 FAILED: patch "[PATCH] KVM: nVMX: update last_nonleaf_level when initializing nested" failed to apply to 4.4-stable tree gregkh
2017-10-16 16:06 ` Paolo Bonzini
2017-10-16 16:13 ` Greg KH [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=20171016161330.GB30572@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=lprosek@redhat.com \
--cc=pbonzini@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox