public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Eli Cohen <eli@mellanox.com>
Cc: mst@redhat.com, virtualization@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org, shahafs@mellanox.com,
	saeedm@mellanox.com, parav@mellanox.com
Subject: Re: [PATCH V3 vhost next 00/10] VDPA support for Mellanox ConnectX devices
Date: Tue, 28 Jul 2020 14:53:34 +0800	[thread overview]
Message-ID: <83eb3fdc-83d5-7f88-bef4-602e60c19662@redhat.com> (raw)
In-Reply-To: <ef857921-4b9a-8e48-d5cd-5ef585e8f15c@redhat.com>


On 2020/7/28 下午2:40, Jason Wang wrote:
>
> On 2020/7/28 下午2:32, Eli Cohen wrote:
>> On Tue, Jul 28, 2020 at 02:18:16PM +0800, Jason Wang wrote:
>>> On 2020/7/28 下午2:05, Eli Cohen wrote:
>>>> Hi Michael,
>>>> please note that this series depends on mlx5 core device driver 
>>>> patches
>>>> in mlx5-next branch in
>>>> git://git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux.git.
>>>>
>>>> git pull 
>>>> git://git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux.git 
>>>> mlx5-next
>>>>
>>>> They also depend Jason Wang's patches submitted a couple of weeks ago.
>>>>
>>>> vdpa_sim: use the batching API
>>>> vhost-vdpa: support batch updating
>>>
>>> Just notice that a new version is posted[1] (you were cced). Talked
>>> with Michael, and it's better for you to merge the new version in
>>> this series.
>>>
>> OK, will send again. Just to make sure, I should put your series and my
>> series on Michal's vhost branch, the same tree I have been using so far?
>
>
> Yes. I think so.
>
> Thanks


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.

Thanks


  reply	other threads:[~2020-07-28  6:53 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-28  6:05 [PATCH V3 vhost next 00/10] VDPA support for Mellanox ConnectX devices Eli Cohen
2020-07-28  6:05 ` [PATCH V3 vhost next 01/10] vhost-vdpa: support batch updating Eli Cohen
2020-07-28  6:05 ` [PATCH V3 vhost next 02/10] vdpa_sim: use the batching API Eli Cohen
2020-07-28  6:05 ` [PATCH V3 vhost next 03/10] vdpa: remove hard coded virtq num Eli Cohen
2020-07-28  6:05 ` [PATCH V3 vhost next 04/10] net/vdpa: Use struct for set/get vq state Eli Cohen
2020-07-28  6:05 ` [PATCH V3 vhost next 05/10] vhost: Fix documentation Eli Cohen
2020-07-28  6:05 ` [PATCH V3 vhost next 06/10] vdpa: Modify get_vq_state() to return error code Eli Cohen
2020-07-28  6:05 ` [PATCH V3 vhost next 07/10] vdpa/mlx5: Add hardware descriptive header file Eli Cohen
2020-07-28  6:05 ` [PATCH V3 vhost next 08/10] vdpa/mlx5: Add support library for mlx5 VDPA implementation Eli Cohen
2020-07-28  6:05 ` [PATCH V3 vhost next 09/10] vdpa/mlx5: Add shared memory registration code Eli Cohen
2020-07-28  6:05 ` [PATCH V3 vhost next 10/10] vdpa/mlx5: Add VDPA driver for supported mlx5 devices Eli Cohen
2020-07-28 13:43   ` kernel test robot
2020-08-04 11:54     ` Eli Cohen
2020-08-04 12:22       ` Michael S. Tsirkin
2020-07-28  6:18 ` [PATCH V3 vhost next 00/10] VDPA support for Mellanox ConnectX devices Jason Wang
2020-07-28  6:32   ` Eli Cohen
2020-07-28  6:40     ` Jason Wang
2020-07-28  6:53       ` Jason Wang [this message]
2020-07-28  6:57         ` Eli Cohen
2020-07-29  5:54         ` Eli Cohen
2020-08-03 20:34           ` Michael S. Tsirkin
2020-08-04  5:33             ` Eli Cohen
2020-08-03 20:51 ` Michael S. Tsirkin
2020-08-04  5:34   ` Eli Cohen
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=83eb3fdc-83d5-7f88-bef4-602e60c19662@redhat.com \
    --to=jasowang@redhat.com \
    --cc=eli@mellanox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --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