From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Wanpeng Li <kernellwp@gmail.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org,
Wanpeng Li <wanpeng.li@hotmail.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] pc: apic: fix touch LAPIC when irqchip is split
Date: Wed, 14 Sep 2016 16:03:58 +0200 [thread overview]
Message-ID: <20160914140357.GB17296@potion> (raw)
In-Reply-To: <20160914140243.GA17296@potion>
2016-09-14 16:02+0200, Radim Krčmář:
> Reviewed-by: Radim Krčmář <rkrcmar@redhat.com>
>
> (The code is horribly tangled, so I might have missed something.)
This reply should have went for the v2, sorry.
prev parent reply other threads:[~2016-09-14 14:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 3:04 [Qemu-devel] [PATCH] pc: apic: fix touch LAPIC when irqchip is split Wanpeng Li
2016-09-14 3:21 ` no-reply
2016-09-14 3:40 ` Fam Zheng
2016-09-14 3:47 ` Wanpeng Li
2016-09-14 14:02 ` Radim Krčmář
2016-09-14 14:03 ` Radim Krčmář [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=20160914140357.GB17296@potion \
--to=rkrcmar@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wanpeng.li@hotmail.com \
/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).