From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: David Miller <davem@davemloft.net>
Cc: mst@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, asias@redhat.com,
pbonzini@redhat.com, stefanha@gmail.com,
stefanha@linux.vnet.ibm.com, wuzhy@cn.ibm.com,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PULL] vhost-net changes for net/3.6
Date: Sun, 22 Jul 2012 13:34:44 -0700 [thread overview]
Message-ID: <1342989284.25472.227.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <20120722.121942.2002727319293471163.davem@davemloft.net>
Hi DaveM,
On Sun, 2012-07-22 at 12:19 -0700, David Miller wrote:
> From: "Michael S. Tsirkin" <mst@redhat.com>
> Date: Sun, 22 Jul 2012 01:54:36 +0300
>
> > The following changes since commit 186e868786f97c8026f0a81400b451ace306b3a4:
> >
> > forcedeth: spin_unlock_irq in interrupt handler fix (2012-07-20 16:18:36 -0700)
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost-net-next
> >
> > for you to fetch changes up to 163049aefdc04323a2d17ec9f2862027b43b0502:
> >
> > vhost: make vhost work queue visible (2012-07-22 01:22:23 +0300)
>
> Pulled, thanks.
So target-pending/for-next-merge will need to be rebased once these bits
hit mainline for the tcm_vhost initial merge commit..
Just curious when your planning on sending out a -rc1 PULL request for
net-next..?
--nab
prev parent reply other threads:[~2012-07-22 20:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-21 22:54 [PULL] vhost-net changes for net/3.6 Michael S. Tsirkin
2012-07-22 19:19 ` David Miller
2012-07-22 20:34 ` Nicholas A. Bellinger [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=1342989284.25472.227.camel@haakon2.linux-iscsi.org \
--to=nab@linux-iscsi.org \
--cc=asias@redhat.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=stefanha@gmail.com \
--cc=stefanha@linux.vnet.ibm.com \
--cc=wuzhy@cn.ibm.com \
/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).