From: Jason Gunthorpe <jgg@ziepe.ca>
To: Leon Romanovsky <leon@kernel.org>
Cc: Doug Ledford <dledford@redhat.com>,
Leon Romanovsky <leonro@mellanox.com>,
RDMA mailing list <linux-rdma@vger.kernel.org>,
Max Gurtovoy <maxg@mellanox.com>,
Yishai Hadas <yishaih@mellanox.com>,
Saeed Mahameed <saeedm@mellanox.com>,
linux-netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH rdma-next 0/2] DEVX VHCA tunnel support
Date: Fri, 5 Jul 2019 14:40:07 -0300 [thread overview]
Message-ID: <20190705174007.GA7787@ziepe.ca> (raw)
In-Reply-To: <20190701181402.25286-1-leon@kernel.org>
On Mon, Jul 01, 2019 at 09:14:00PM +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@mellanox.com>
>
> Hi,
>
> Those two patches introduce VHCA tunnel mechanism to DEVX interface
> needed for Bluefield SOC. See extensive commit messages for more
> information.
>
> Thanks
>
> Max Gurtovoy (2):
> net/mlx5: Introduce VHCA tunnel device capability
> IB/mlx5: Implement VHCA tunnel mechanism in DEVX
>
> drivers/infiniband/hw/mlx5/devx.c | 24 ++++++++++++++++++++----
> include/linux/mlx5/mlx5_ifc.h | 10 ++++++++--
> 2 files changed, 28 insertions(+), 6 deletions(-)
This looks Ok can you apply the mlx5-next patch please
Thanks,
Jason
next prev parent reply other threads:[~2019-07-05 17:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 18:14 [PATCH rdma-next 0/2] DEVX VHCA tunnel support Leon Romanovsky
2019-07-01 18:14 ` [PATCH mlx5-next 1/2] net/mlx5: Introduce VHCA tunnel device capability Leon Romanovsky
2019-07-01 18:14 ` [PATCH rdma-next 2/2] IB/mlx5: Implement VHCA tunnel mechanism in DEVX Leon Romanovsky
2019-07-05 17:40 ` Jason Gunthorpe [this message]
2019-07-07 7:51 ` [PATCH rdma-next 0/2] DEVX VHCA tunnel support Leon Romanovsky
2019-07-08 16:58 ` Jason Gunthorpe
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=20190705174007.GA7787@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dledford@redhat.com \
--cc=leon@kernel.org \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=maxg@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
--cc=yishaih@mellanox.com \
/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).