netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>,
	Artemy Kovalyov <artemyko@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] Fix to mlx5 devx interface
Date: Thu, 20 Dec 2018 14:01:07 -0700	[thread overview]
Message-ID: <20181220210107.GA10152@ziepe.ca> (raw)
In-Reply-To: <20181219142811.21301-1-leon@kernel.org>

On Wed, Dec 19, 2018 at 04:28:09PM +0200, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@mellanox.com>
> 
> Hi,
> 
> This small fix to mlx5 devx interface is separated to two, so we can
> apply first patch to mlx5-next.
> 
> Thanks
> 
> Yishai Hadas (2):
>   IB/mlx5: Introduce uid as part of alloc/dealloc transport domain
>   IB/mlx5: Use uid as part of alloc/dealloc transport domain
> 
>  drivers/infiniband/hw/mlx5/cmd.c | 2 ++
>  include/linux/mlx5/mlx5_ifc.h    | 4 ++--
>  2 files changed, 4 insertions(+), 2 deletions(-)

Applied to for-next

Thanks,
Jason

      parent reply	other threads:[~2018-12-20 21:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-19 14:28 [PATCH rdma-next 0/2] Fix to mlx5 devx interface Leon Romanovsky
2018-12-19 14:28 ` [PATCH mlx5-next 1/2] IB/mlx5: Introduce uid as part of alloc/dealloc transport domain Leon Romanovsky
2018-12-19 14:28 ` [PATCH rdma-next 2/2] IB/mlx5: Use " Leon Romanovsky
2018-12-19 19:14 ` [PATCH rdma-next 0/2] Fix to mlx5 devx interface Jason Gunthorpe
2018-12-20  6:11   ` Leon Romanovsky
2018-12-20 21:01 ` Jason Gunthorpe [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=20181220210107.GA10152@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=artemyko@mellanox.com \
    --cc=dledford@redhat.com \
    --cc=leon@kernel.org \
    --cc=leonro@mellanox.com \
    --cc=linux-rdma@vger.kernel.org \
    --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).