From: Avi Kivity <avi@redhat.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [PATCH 04/08]kvm: Split arch/x86/kvm/irq.c to two parts.
Date: Wed, 08 Oct 2008 13:39:17 +0000 [thread overview]
Message-ID: <48ECB805.2020504@redhat.com> (raw)
In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDC01ABCA37@pdsmsx415.ccr.corp.intel.com>
Zhang, Xiantao wrote:
> Avi Kivity wrote:
>
>> Zhang, Xiantao wrote:
>>
>>> Hi, Avi
>>> I have fixed it on my ia32 machine but seems forget to commit
>>> it.Okay, I will retest it before sending out the new one.
>>>
>>>
>> If it's just a small fix, please send and incremental patch and I will
>> merge it with the patch it fixes.
>>
>
> Yes, it is just a small fix. irq.h should be included for irq_comm.c,
> but seems forget it in the patch. Sorry for that.
>
Okay, I updated the patch and pushed it out. Thanks.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
prev parent reply other threads:[~2008-10-08 13:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 1:51 [PATCH 04/08]kvm: Split arch/x86/kvm/irq.c to two parts Zhang, Xiantao
2008-10-08 11:02 ` Avi Kivity
2008-10-08 11:08 ` Zhang, Xiantao
2008-10-08 11:13 ` Avi Kivity
2008-10-08 11:52 ` Zhang, Xiantao
2008-10-08 13:39 ` Avi Kivity [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=48ECB805.2020504@redhat.com \
--to=avi@redhat.com \
--cc=kvm-ia64@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