From: Rusty Russell <rusty@rustcorp•com.au>
To: "linux-next@vger•kernel.org" <linux-next@vger•kernel.org>
Cc: "Michael S. Tsirkin" <mst@redhat•com>
Subject: virtio-next tree
Date: Sat, 02 May 2015 08:44:28 +0930 [thread overview]
Message-ID: <87egmz3n6z.fsf@rustcorp.com.au> (raw)
Hi Stephen,
As promised, there will be no new updates to the virtio-next
tree. I don't know if MST wants to overload his vhost tree or start a
new virtio-next tree.
BTW, Muchael, I only had one typo patch so far for next merge window,
and I just posted that.
Cheers,
Rusty.
next reply other threads:[~2015-05-01 23:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 23:14 Rusty Russell [this message]
2015-05-01 23:45 ` virtio-next tree Stephen Rothwell
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=87egmz3n6z.fsf@rustcorp.com.au \
--to=rusty@rustcorp$(echo .)com.au \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mst@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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