From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: David Miller <davem@davemloft.net>,
kvm@vger.kernel.org, virtualization@lists.osdl.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
asias@redhat.com
Subject: Re: [PULL] vhost: cleanups and fixes for 3.10
Date: Wed, 1 May 2013 20:00:06 +0300 [thread overview]
Message-ID: <20130501170006.GA22236@redhat.com> (raw)
In-Reply-To: <1367424335.10977.2.camel@haakon3.risingtidesystems.com>
On Wed, May 01, 2013 at 09:05:35AM -0700, Nicholas A. Bellinger wrote:
> On Wed, 2013-05-01 at 18:01 +0300, Michael S. Tsirkin wrote:
> > Please pull the following vhost core updates for 3.10 -
> > they affect both vhost-net and vhost-scsi devices.
> > They also *depend* on both net-next and target-pending. Since Linus
> > merged target-pending but not net-next at this point, merging through
> > the net tree seems to make sense.
> >
>
> Perfectly fine by me..
>
> Btw, I'll be sending another PULL request next week for some other minor
> -rc1 items, so if DaveM prefers I'm happy to include this series in that
> PULL instead.
>
> --nab
Yes but it depends on stuff in net-next. That would pull in a lot.
> > The following changes since commit bc7562355fda8075793bf66094cda573206ec693:
> >
> > Merge branch 'for-next-merge' of git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending into vhost-net-next (2013-05-01 09:16:50 +0300)
> >
> > 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 150b9e51ae975ca1fe468c565870fbc4a96e0574:
> >
> > vhost: fix error handling in RESET_OWNER ioctl (2013-05-01 10:02:54 +0300)
> >
> > ----------------------------------------------------------------
> > Asias He (3):
> > vhost: Allow device specific fields per vq
> > tcm_vhost: Wait for pending requests in vhost_scsi_flush()
> > vhost: move vhost-net zerocopy fields to net.c
> >
> > Michael S. Tsirkin (4):
> > tcm_vhost: document inflight ref-counting use
> > vhost: move per-vq net specific fields out to net
> > tcm_vhost: remove virtio-net.h dependency
> > vhost: fix error handling in RESET_OWNER ioctl
> >
> > drivers/vhost/net.c | 255 ++++++++++++++++++++++++++++++++++++----------
> > drivers/vhost/tcm_vhost.c | 154 ++++++++++++++++++++++++----
> > drivers/vhost/tcm_vhost.h | 3 +
> > drivers/vhost/test.c | 9 +-
> > drivers/vhost/vhost.c | 153 +++++++++-------------------
> > drivers/vhost/vhost.h | 32 +-----
> > 6 files changed, 400 insertions(+), 206 deletions(-)
>
next prev parent reply other threads:[~2013-05-01 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 15:01 [PULL] vhost: cleanups and fixes for 3.10 Michael S. Tsirkin
2013-05-01 16:05 ` Nicholas A. Bellinger
2013-05-01 17:00 ` Michael S. Tsirkin [this message]
2013-05-01 19:05 ` David Miller
2013-05-02 1:46 ` 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=20130501170006.GA22236@redhat.com \
--to=mst@redhat.com \
--cc=asias@redhat.com \
--cc=davem@davemloft.net \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.osdl.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).