From: Avi Kivity <avi@redhat.com>
To: Gregory Haskins <ghaskins@novell.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
davdel@xmailserver.org, mst@redhat.com,
paulmck@linux.vnet.ibm.com, akpm@linux-foundation.org
Subject: Re: [KVM PATCH v2 0/2] irqfd: use POLLHUP notification for close()
Date: Thu, 04 Jun 2009 17:02:04 +0300 [thread overview]
Message-ID: <4A27D3DC.7080400@redhat.com> (raw)
In-Reply-To: <20090604124047.10544.38861.stgit@dev.haskins.net>
Gregory Haskins wrote:
> (Applies to kvm.git/master:25deed73)
>
> Please see the header for 2/2 for a description. This patch series has been
> fully tested and appears to be working correctly.
>
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-06-04 14:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 12:48 [KVM PATCH v2 0/2] irqfd: use POLLHUP notification for close() Gregory Haskins
2009-06-04 12:48 ` [KVM PATCH v2 1/2] Allow waiters to be notified about the eventfd file* going away, and give Gregory Haskins
2009-06-04 12:48 ` [KVM PATCH v2 2/2] kvm: use POLLHUP to close an irqfd instead of an explicit ioctl Gregory Haskins
2009-06-14 11:49 ` Michael S. Tsirkin
2009-06-14 12:53 ` Gregory Haskins
2009-06-14 13:28 ` Michael S. Tsirkin
2009-06-15 3:39 ` Gregory Haskins
2009-06-15 9:46 ` Michael S. Tsirkin
2009-06-15 12:08 ` Gregory Haskins
2009-06-15 12:54 ` Michael S. Tsirkin
2009-06-18 5:16 ` Rusty Russell
2009-06-18 6:49 ` Michael S. Tsirkin
2009-06-18 12:00 ` Gregory Haskins
2009-06-18 12:22 ` Michael S. Tsirkin
2009-06-18 14:03 ` Gregory Haskins
2009-06-18 14:35 ` Michael S. Tsirkin
2009-06-18 16:29 ` Gregory Haskins
2009-06-19 15:37 ` Michael S. Tsirkin
2009-06-19 16:07 ` Gregory Haskins
2009-06-15 3:48 ` Gregory Haskins
2009-06-04 14:02 ` Avi Kivity [this message]
2009-06-12 3:58 ` [KVM PATCH v2 0/2] irqfd: use POLLHUP notification for close() Michael S. Tsirkin
2009-06-12 4:08 ` Michael S. Tsirkin
2009-06-14 12:38 ` Gregory Haskins
2009-06-14 12:51 ` Avi Kivity
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=4A27D3DC.7080400@redhat.com \
--to=avi@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=davdel@xmailserver.org \
--cc=ghaskins@novell.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=paulmck@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.