From: Avi Kivity <avi@redhat.com>
To: Chris Lalancette <clalance@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] Search the LAPIC's for one that will accept a PIC interrupt.
Date: Thu, 24 Jun 2010 06:43:24 +0300 [thread overview]
Message-ID: <4C22D45C.3030902@redhat.com> (raw)
In-Reply-To: <20100623205619.GH2767@localhost.localdomain>
On 06/23/2010 11:56 PM, Chris Lalancette wrote:
>
> Did you forget to push out a tree with this patch applied, or are you doing
> some testing before doing so? I don't see this patch in the current kvm
> tree (git head is a63e16c655f9e68d49d6fae4275ffda16b1888b2).
>
No and yes. Under testing patches are queued in the 'next' branch;
after testing they are merged into 'master'.
Use 'git fetch' instead of 'git pull' to see all branches.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
prev parent reply other threads:[~2010-06-24 3:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 15:29 [PATCH] Search the LAPIC's for one that will accept a PIC interrupt Chris Lalancette
2010-06-22 8:10 ` Gleb Natapov
2010-06-22 11:34 ` Avi Kivity
2010-06-22 11:49 ` Gleb Natapov
2010-06-22 11:54 ` Avi Kivity
2010-06-23 11:37 ` Avi Kivity
[not found] ` <20100623205619.GH2767@localhost.localdomain>
2010-06-24 3:43 ` 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=4C22D45C.3030902@redhat.com \
--to=avi@redhat.com \
--cc=clalance@redhat.com \
--cc=kvm@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