virtualization.lists.linux-foundation.org archive mirror
 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
Subject: Re: virtio for 3.20
Date: Thu, 22 Jan 2015 11:29:44 +1030	[thread overview]
Message-ID: <8761bzwry7.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20150121174017.GA21032@redhat.com>

"Michael S. Tsirkin" <mst@redhat.com> writes:
> On Mon, Jan 19, 2015 at 12:56:28PM +1030, Rusty Russell wrote:
>> "Michael S. Tsirkin" <mst@redhat.com> writes:
>> > Hi Rusty, all
>> >
>> > I parked outstanding virtio patches here:
>> > git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost-next
>> > this way they are merged in linux-next as well.
>> >
>> > Rusty if you'll be doing 3.20 window, would you mind
>> > checking that tree to verify nothing's lost?
>> 
>> Hi Michael,
>> 
>>         Thanks, now I've returned from linux.conf.au, I'm starting to
>> organize the 3.20 queue.  I've merged this branch into my virtio-next
>> branch.
>> 
>> Cheers,
>> Rusty.
>
> Thanks, good to know.
> I tweaked some patches since due to test failure reports by Gerd.
> Updated patches are tagged "post-squash", if you want to see what
> changed, see fixup patches in the series tagged "pre-squash".
>
> Or you can look at my tree:
>         git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git virtio-next
> is pre-squash.
>         git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost-next
> is post-squash.

OK, I merged your vhost-next with my virtio-next, and the merge was
empty.

So we're up-to-date.  Please send patches against my virtio-next from
now on.

Thanks,
Rusty.

  reply	other threads:[~2015-01-22  0:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-15 18:36 virtio for 3.20 Michael S. Tsirkin
2015-01-19  2:26 ` Rusty Russell
2015-01-21 17:40   ` Michael S. Tsirkin
2015-01-22  0:59     ` Rusty Russell [this message]
2015-01-22  9:57       ` 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=8761bzwry7.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).