From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, jasowang@redhat.com, mashirle@us.ibm.com
Subject: Re: [PULL net-next] vhost-net fixes for 3.1
Date: Tue, 19 Jul 2011 22:05:39 +0300 [thread overview]
Message-ID: <20110719190539.GA8667@redhat.com> (raw)
In-Reply-To: <20110719.120007.1487641546240582444.davem@davemloft.net>
On Tue, Jul 19, 2011 at 12:00:07PM -0700, David Miller wrote:
> From: "Michael S. Tsirkin" <mst@redhat.com>
> Date: Tue, 19 Jul 2011 21:58:13 +0300
>
> > I have snuck in another one:
> > vhost: optimize interrupt enable/disable
> >
> > please don't be alarmed :)
>
> I already pulled so send another pull request if you want me
> to get this.
You got the new one actually, so nothing needs to be done,
I think.
Thanks!
--
MST
prev parent reply other threads:[~2011-07-19 19:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 11:47 [PULL net-next] vhost-net fixes for 3.1 Michael S. Tsirkin
2011-07-19 17:15 ` David Miller
2011-07-19 18:58 ` Michael S. Tsirkin
2011-07-19 19:00 ` David Miller
2011-07-19 19:05 ` Michael S. Tsirkin [this message]
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=20110719190539.GA8667@redhat.com \
--to=mst@redhat.com \
--cc=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=mashirle@us.ibm.com \
--cc=netdev@vger.kernel.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).