virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Eli Cohen <eli@mellanox.com>
Cc: shahafs@mellanox.com, parav@mellanox.com,
	linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org, saeedm@mellanox.com
Subject: Re: [PATCH V3 vhost next 00/10] VDPA support for Mellanox ConnectX devices
Date: Mon, 3 Aug 2020 16:34:50 -0400	[thread overview]
Message-ID: <20200803163235-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20200729055452.GA31247@mtl-vdi-166.wap.labs.mlnx>

On Wed, Jul 29, 2020 at 08:54:52AM +0300, Eli Cohen wrote:
> On Tue, Jul 28, 2020 at 02:53:34PM +0800, Jason Wang wrote:
> > 
> > Just notice Michael's vhost branch can not compile due to this commit:
> > 
> > commit fee8fe6bd8ccacd27e963b71b4f943be3721779e
> > Author: Michael S. Tsirkin <mst@redhat.com>
> > Date:   Mon Jul 27 10:51:55 2020 -0400
> > 
> >     vdpa: make sure set_features in invoked for legacy
> > 
> > Let's wait for Michael to clarify the correct branch to use then.
> >
> 
> Michael, are you going to send a path to a git tree that I can rebase my
> series on top of it, or maybe you can just take my v3 and apply them on
> the right tree? If you do, you can take Jason's patches from the series
> he posted here https://lkml.org/lkml/2020/7/1/301 and take my 0003-0010
> patches.
> 
> Let me know.

It's a bit too hard to figure out how to put these pieces together, when
I tried I run into some conflicts, and given I can't test them I'd
rather you did this.  Please also note kbuild test bot reported a build
failure on mips.

A good tree to base your work on is the linux-next branch
in https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git

Thanks!
-- 
MST

_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

       reply	other threads:[~2020-08-03 20:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200728060539.4163-1-eli@mellanox.com>
     [not found] ` <1dbac14a-5909-ff0a-8e90-534847f93d50@redhat.com>
     [not found]   ` <20200728063211.GA229972@mtl-vdi-166.wap.labs.mlnx>
     [not found]     ` <ef857921-4b9a-8e48-d5cd-5ef585e8f15c@redhat.com>
     [not found]       ` <83eb3fdc-83d5-7f88-bef4-602e60c19662@redhat.com>
     [not found]         ` <20200729055452.GA31247@mtl-vdi-166.wap.labs.mlnx>
2020-08-03 20:34           ` Michael S. Tsirkin [this message]
2020-08-03 20:51 ` [PATCH V3 vhost next 00/10] VDPA support for Mellanox ConnectX devices Michael S. Tsirkin
     [not found]   ` <20200804053432.GB58580@mtl-vdi-166.wap.labs.mlnx>
2020-08-04  9:39     ` 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=20200803163235-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=eli@mellanox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=parav@mellanox.com \
    --cc=saeedm@mellanox.com \
    --cc=shahafs@mellanox.com \
    --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;
as well as URLs for NNTP newsgroup(s).