From: Paolo Bonzini <pbonzini@redhat.com>
To: Greg KH <gregkh@linuxfoundation.org>, Matt Gingell <gingell@google.com>
Cc: stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] KVM: x86: fix interrupt window handling in split IRQ chip" failed to apply to 4.3-stable tree
Date: Wed, 9 Dec 2015 15:57:40 +0100 [thread overview]
Message-ID: <56684164.7060408@redhat.com> (raw)
In-Reply-To: <20151207233228.GA6344@kroah.com>
On 08/12/2015 00:32, Greg KH wrote:
> On Mon, Dec 07, 2015 at 03:27:20PM -0800, Matt Gingell wrote:
>> These can wait for 4.4.
>
> Then why were they marked for stable?
Even though the bugs were found while testing a new feature in 4.4, the
bug exists in 4.3 as well. The patches don't apply because of the
context changes caused by the new feature.
I'll do the backport and post them to stable@vger.kernel.org.
Paolo
prev parent reply other threads:[~2015-12-09 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 7:37 FAILED: patch "[PATCH] KVM: x86: fix interrupt window handling in split IRQ chip" failed to apply to 4.3-stable tree gregkh
2015-12-07 23:27 ` Matt Gingell
2015-12-07 23:32 ` Greg KH
2015-12-09 14:57 ` Paolo Bonzini [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=56684164.7060408@redhat.com \
--to=pbonzini@redhat.com \
--cc=gingell@google.com \
--cc=gregkh@linuxfoundation.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).