All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: virtualization@lists.linux-foundation.org, markmc@redhat.com,
	Anthony Liguori <anthony@codemonkey.ws>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [PATCH] virtio-spec: document indirect descriptors
Date: Thu, 11 Feb 2010 09:54:08 +1030	[thread overview]
Message-ID: <201002110954.09134.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20100210130026.GA19271@redhat.com>

On Wed, 10 Feb 2010 11:30:39 pm Michael S. Tsirkin wrote:
> Add documentation for indirect descriptors

Thanks, that's awesome!

I added an entry to the Reserved Feature table in appendix B, and applied
it.  We're now at 0.8.5.

Cheers,
Rusty.

WARNING: multiple messages have this Message-ID (diff)
From: Rusty Russell <rusty@rustcorp.com.au>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: markmc@redhat.com, kvm@vger.kernel.org, qemu-devel@nongnu.org,
	virtualization@lists.linux-foundation.org
Subject: [Qemu-devel] Re: [PATCH] virtio-spec: document indirect descriptors
Date: Thu, 11 Feb 2010 09:54:08 +1030	[thread overview]
Message-ID: <201002110954.09134.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20100210130026.GA19271@redhat.com>

On Wed, 10 Feb 2010 11:30:39 pm Michael S. Tsirkin wrote:
> Add documentation for indirect descriptors

Thanks, that's awesome!

I added an entry to the Reserved Feature table in appendix B, and applied
it.  We're now at 0.8.5.

Cheers,
Rusty.

  reply	other threads:[~2010-02-10 23:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-10 13:00 [PATCH] virtio-spec: document indirect descriptors Michael S. Tsirkin
2010-02-10 13:00 ` [Qemu-devel] " Michael S. Tsirkin
2010-02-10 23:24 ` Rusty Russell [this message]
2010-02-10 23:24   ` [Qemu-devel] " Rusty Russell
2010-02-10 23:24 ` Rusty Russell
  -- strict thread matches above, loose matches on Subject: below --
2010-02-10 13:00 Michael S. Tsirkin

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=201002110954.09134.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=anthony@codemonkey.ws \
    --cc=kvm@vger.kernel.org \
    --cc=markmc@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=virtualization@lists.linux-foundation.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.