virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: kvm@vger.kernel.org, virtualization@lists.osdl.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	agrover@redhat.com, asias@redhat.com, brian@purestorage.com,
	hch@lst.de, joern@logfs.org, mark.d.rustad@intel.com,
	martin.petersen@oracle.com, nab@linux-iscsi.org,
	ogerlitz@mellanox.com, yongjun_wei@trendmicro.com.cn
Subject: Re: [PULL] vhost: cleanups and fixes for 3.10
Date: Thu, 2 May 2013 04:46:26 +0300	[thread overview]
Message-ID: <20130502014626.GA26105@redhat.com> (raw)
In-Reply-To: <20130501.150548.1959140741961524114.davem@davemloft.net>

On Wed, May 01, 2013 at 03:05:48PM -0400, David Miller wrote:
> From: "Michael S. Tsirkin" <mst@redhat.com>
> Date: Wed, 1 May 2013 18:01:31 +0300
> 
> > 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.
> 
> I don't have target-pending in my tree though and I'm not going to pull
> it in just for this.
> 
> Since you have such a multi-dependency situation, just ask Linus to pull
> this directly after I push net-next to him, which should be later today.
> 
> Thanks.

OK, thanks.

      reply	other threads:[~2013-05-02  1:46 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
2013-05-01 19:05 ` David Miller
2013-05-02  1:46   ` 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=20130502014626.GA26105@redhat.com \
    --to=mst@redhat.com \
    --cc=agrover@redhat.com \
    --cc=asias@redhat.com \
    --cc=brian@purestorage.com \
    --cc=davem@davemloft.net \
    --cc=hch@lst.de \
    --cc=joern@logfs.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.d.rustad@intel.com \
    --cc=martin.petersen@oracle.com \
    --cc=nab@linux-iscsi.org \
    --cc=netdev@vger.kernel.org \
    --cc=ogerlitz@mellanox.com \
    --cc=virtualization@lists.osdl.org \
    --cc=yongjun_wei@trendmicro.com.cn \
    /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).