public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	virtualization@lists.linux-foundation.org,
	netdev <netdev@vger.kernel.org>
Subject: Re: Rusty away 18th September -- 11th October
Date: Fri, 12 Sep 2014 10:58:03 +0930	[thread overview]
Message-ID: <87tx4dhbks.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20140911114351.GA25736@redhat.com>

"Michael S. Tsirkin" <mst@redhat.com> writes:
> On Thu, Sep 11, 2014 at 10:26:52AM +0930, Rusty Russell wrote:
>> Hi all,
>> 
>>         Probably won't read mail.  Linus, I'll have pull requests early
>> next week; if there's anything needed I'm sure Michael Tsirkin can
>> handle it.
>
> Sure.
> Rusty, there's a small chance virtio 1.0 bits will be ready in time.
> I started working on them based on your virtio-pci-new-layout branch.
>
> If ready before the merge window, are you ok with me merging this
> support (without you having the opportunity to review first)?

Sorry, absolutely not.  I *really* want to review this in depth; if we
make a mistake, it's going to hurt us significantly.

And until we have the qemu bits ready, it's really hard to tell if we've
got this right.  So I'd rather delay and make sure we're solid.

Thanks,
Rusty.

  reply	other threads:[~2014-09-13  5:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-11  0:56 Rusty away 18th September -- 11th October Rusty Russell
2014-09-11 11:43 ` Michael S. Tsirkin
2014-09-12  1:28   ` Rusty Russell [this message]
2014-09-14  6:21     ` Michael S. Tsirkin
2014-09-16 15:53       ` Rusty Russell
2014-09-16 16:20         ` Michael S. Tsirkin
2014-09-11 20:16 ` Linus Torvalds

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=87tx4dhbks.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox