From: David Hildenbrand <david@redhat.com>
To: Dmitry Vyukov <dvyukov@google.com>, Paolo Bonzini <pbonzini@redhat.com>
Cc: "Radim Krčmář" <rkrcmar@redhat.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>,
"KVM list" <kvm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"Steve Rutherford" <srutherford@google.com>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: kvm: WARNING In kvm_apic_accept_events
Date: Wed, 22 Mar 2017 16:35:55 +0100 [thread overview]
Message-ID: <0a9b8a17-a1c3-d732-8016-cca3f4c9894b@redhat.com> (raw)
In-Reply-To: <CACT4Y+abkqgb0Q-Te7e7UTFpEUjsDwTNEmNYN5pLR8tgqtA5PQ@mail.gmail.com>
On 22.03.2017 16:34, Dmitry Vyukov wrote:
> On Wed, Feb 15, 2017 at 11:10 AM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>>
>>
>> On 15/02/2017 10:26, David Hildenbrand wrote:
>>>>
>>>> Any progress with this? Should we commit this as is?
>>>>
>>> Paolo, should I resend as a proper notcopieddiff mail?
>>
>> Yes, please do (CCing stable@vger.kernel.org too).
>>
>> Paolo
>
> Has this reached any tree? I don't see this in kvm/master.
>
Whops, seems like I missed Paolo's mail. Will send out the patch in a
minute.
--
Thanks,
David
next prev parent reply other threads:[~2017-03-22 15:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-12 1:56 Dmitry Vyukov
2017-01-22 8:52 ` Dmitry Vyukov
2017-01-23 16:03 ` David Hildenbrand
2017-01-23 16:29 ` Paolo Bonzini
2017-02-14 20:31 ` Dmitry Vyukov
2017-02-15 9:26 ` David Hildenbrand
2017-02-15 10:10 ` Paolo Bonzini
2017-03-22 15:34 ` Dmitry Vyukov
2017-03-22 15:35 ` David Hildenbrand [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-01-08 17:16 kvm: WARNING in kvm_apic_accept_events Dmitry Vyukov
2016-01-15 17:13 ` Dmitry Vyukov
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=0a9b8a17-a1c3-d732-8016-cca3f4c9894b@redhat.com \
--to=david@redhat.com \
--cc=dvyukov@google.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=srutherford@google.com \
--cc=syzkaller@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®