All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Ahern" <daahern@cisco.com>
To: Chris Wright <chrisw@redhat.com>, qemu-devel@nongnu.org
Cc: kvm@vger.kernel.org, Cam Macdonell <cam@cs.ualberta.ca>
Subject: Re: KVM call minutes for July 20
Date: Tue, 20 Jul 2010 10:40:05 -0600	[thread overview]
Message-ID: <4C45D165.4060406@cisco.com> (raw)
In-Reply-To: <20100720144551.GB32665@x200.localdomain>



On 07/20/10 08:45, Chris Wright wrote:
> 0.13
> - rc RSN (hopefully this week, top priority for anthony)

Can Cam's inter-vm shared memory device get committed for 0.13? It's
been stagnant on the list for a while now waiting for inclusion (or NAK
comments).

David

WARNING: multiple messages have this Message-ID (diff)
From: "David S. Ahern" <daahern@cisco.com>
To: Chris Wright <chrisw@redhat.com>, qemu-devel@nongnu.org
Cc: Cam Macdonell <cam@cs.ualberta.ca>, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: KVM call minutes for July 20
Date: Tue, 20 Jul 2010 10:40:05 -0600	[thread overview]
Message-ID: <4C45D165.4060406@cisco.com> (raw)
In-Reply-To: <20100720144551.GB32665@x200.localdomain>



On 07/20/10 08:45, Chris Wright wrote:
> 0.13
> - rc RSN (hopefully this week, top priority for anthony)

Can Cam's inter-vm shared memory device get committed for 0.13? It's
been stagnant on the list for a while now waiting for inclusion (or NAK
comments).

David

  parent reply	other threads:[~2010-07-20 16:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-20 14:45 KVM call minutes for July 20 Chris Wright
2010-07-20 14:45 ` [Qemu-devel] " Chris Wright
2010-07-20 16:29 ` Aurelien Jarno
2010-07-20 16:29   ` Aurelien Jarno
2010-07-20 17:55   ` Anthony Liguori
2010-07-20 17:55     ` Anthony Liguori
2010-07-20 16:40 ` David S. Ahern [this message]
2010-07-20 16:40   ` [Qemu-devel] " David S. Ahern

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=4C45D165.4060406@cisco.com \
    --to=daahern@cisco.com \
    --cc=cam@cs.ualberta.ca \
    --cc=chrisw@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.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 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.