DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shachar Beiser <shacharbe@mellanox.com>
To: Alexey Perevalov <a.perevalov@samsung.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v1] net/mlx5: support upstream rdma-core
Date: Mon, 4 Sep 2017 06:30:53 +0000	[thread overview]
Message-ID: <AM2PR05MB0689F0BC6706E3FE4C9196D0C0910@AM2PR05MB0689.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <51db3c99-414f-8272-1061-c5fee3bb295a@samsung.com>

Yes , off course .
In my next patch the rdma-core is master f11292efd54132e09c9586a72c6c7bd0f341659d.
I will add that to the patch in the cover letter.
         -Shachar Beiser.


shacharbe@pegasus08-006:~/rdma-core$ git remote --v
origin  http://l-gerrit.mtl.labs.mlnx:8080/upstream/rdma-core.git (fetch)
origin  http://l-gerrit.mtl.labs.mlnx:8080/upstream/rdma-core.git (push)
shacharbe@pegasus08-006:~/rdma-core$ git branch
* master
shacharbe@pegasus08-006:~/rdma-core$ git log
commit f11292efd54132e09c9586a72c6c7bd0f341659d
Merge: 1435758 210e715
Author: Doug Ledford <dledford@redhat.com>
Date:   Sat Sep 2 09:06:16 2017 -0400

    Merge pull request #202 from yishaih/mlx5_dv

    mlx5 dv



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Alexey Perevalov
> Sent: Thursday, August 31, 2017 7:18 PM
> To: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v1] net/mlx5: support upstream rdma-core
> 
> Hello Shachar,
> 
> Thank you for the patch.
> 
> 
> Please could you specify patch set you used in new version, IIUC,
> 
> it's [PATCH 0/5] net/mlx5: cleanups" and [PATCH 0/5] net/mlx5:
> enable/disable vPMD and some cleanups
> 
> by Nélio Laranjeiro.
> 
> Also rdma-core version, I used HEAD (commit
> 202b39622e67b0424b2598fc6dd1c546e42f9edb),
> 
> but I had to revert "mlx5: Fix ABI break from revising the UAR pointer".
> 
> 
> --
> Best regards,
> Alexey Perevalov

  reply	other threads:[~2017-09-04  6:30 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-24 12:23 Shachar Beiser
2017-08-24 13:43 ` Ferruh Yigit
2017-08-24 14:59 ` Nélio Laranjeiro
     [not found] ` <CGME20170831161745eucas1p112753dbc96b3b209d303b007dda0408b@eucas1p1.samsung.com>
2017-08-31 16:17   ` Alexey Perevalov
2017-09-04  6:30     ` Shachar Beiser [this message]
2017-09-04 12:07 ` [dpdk-dev] [PATCH v2] " Shachar Beiser
2017-09-04 14:42   ` Nélio Laranjeiro
2017-09-05 13:19   ` [dpdk-dev] [PATCH v3] " Shachar Beiser
2017-09-05 13:44     ` Nélio Laranjeiro
2017-09-07 12:55     ` [dpdk-dev] [PATCH v4] " Shachar Beiser
2017-09-07 14:55       ` Nélio Laranjeiro
2017-09-14 13:34       ` [dpdk-dev] [PATCH v5] " Shachar Beiser
2017-09-14 13:47         ` Ferruh Yigit
2017-09-17  7:31           ` Shachar Beiser
2017-09-18  8:52             ` Shahaf Shuler
2017-09-18  9:07             ` Ferruh Yigit
2017-09-18 13:43               ` Shachar Beiser
2017-09-18 16:04                 ` Yigit, Ferruh
2017-09-17 10:10         ` [dpdk-dev] [PATCH v6] " Shachar Beiser
2017-09-18 13:53           ` [dpdk-dev] [PATCH v7] " Shachar Beiser
2017-09-18 14:49         ` Shachar Beiser
2017-09-20 12:23           ` Nélio Laranjeiro
2017-09-20 15:48           ` Ferruh Yigit
2017-09-26 15:38           ` [dpdk-dev] [PATCH v8] " Nelio Laranjeiro
2017-09-28 15:40             ` Ferruh Yigit

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=AM2PR05MB0689F0BC6706E3FE4C9196D0C0910@AM2PR05MB0689.eurprd05.prod.outlook.com \
    --to=shacharbe@mellanox.com \
    --cc=a.perevalov@samsung.com \
    --cc=dev@dpdk.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).