From: Rusty Russell <rusty@rustcorp.com.au>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: virtualization@lists.linux-foundation.org
Subject: Re: 2.6.40 event idx patches
Date: Wed, 25 May 2011 11:34:07 +0930 [thread overview]
Message-ID: <87y61vilig.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20110524092345.GA17087@redhat.com>
On Tue, 24 May 2011 12:23:45 +0300, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> Just checking: were you going to send the following to Linus for 2.6.40?
> virtio:event_index_interface.patch
> virtio:ring_inline_function_to_check_for_events.patch
> virtio:ring_support_event_idx_feature.patch
> misc:vhost_support_event_index.patch
> virtio:test_support_event_index.patch
> virtio:add_api_for_delayed_callbacks.patch
> virtio:net_delay_tx_callbacks.patch
>
> I certainly hope so as these modify both host and guest which makes
> testing them out of tree hard for people.
> Once stuff lands on Linus' tree we can patch
> qemu and get more people to try out the patches.
>
> Also, Linus said it's going to be a short window so ...
Yes. They've been in linux-next since the weekend (ie. today will be the
third linux-next build), and my plan was to push them Friday.
Nothing goes into linux-next which is not for Linus until after Linus
closes the merge window.
I also want to find a few cycles to adapt lguest; it's *always* good to
have a second implementation.
Cheers,
Rusty.
next prev parent reply other threads:[~2011-05-25 2:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 9:23 2.6.40 event idx patches Michael S. Tsirkin
2011-05-25 2:04 ` Rusty Russell [this message]
2011-05-25 6:10 ` Michael S. Tsirkin
2011-05-28 19:34 ` Michael S. Tsirkin
2011-05-28 19:42 ` 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=87y61vilig.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=mst@redhat.com \
--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.