Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Doug Ledford <dledford@redhat.com>,
	linux-rdma@vger.kernel.org, Saeed Mahameed <saeedm@nvidia.com>,
	Yishai Hadas <yishaih@mellanox.com>,
	Yishai Hadas <yishaih@nvidia.com>
Subject: Re: [PATCH mlx5-next 0/3] Cleanup around DEVX get/set commands
Date: Tue, 19 Jan 2021 07:36:39 +0200	[thread overview]
Message-ID: <20210119053639.GA21258@unreal> (raw)
In-Reply-To: <20210118200031.GA729141@nvidia.com>

On Mon, Jan 18, 2021 at 04:00:31PM -0400, Jason Gunthorpe wrote:
> On Wed, Dec 30, 2020 at 03:01:18PM +0200, Leon Romanovsky wrote:
> > From: Leon Romanovsky <leonro@nvidia.com>
> >
> > Be more strict with DEVX get/set operations for the obj_id.
> >
> > Yishai Hadas (3):
> >   RDMA/mlx5: Use the correct obj_id upon DEVX TIR creation
> >   net/mlx5: Expose ifc bits for query modify header
> >   RDMA/mlx5: Use strict get/set operations for obj_id
>
> This looks fine, can you update the shared branch with the ifc update
> please

Thanks, I added only one commit ab0da5a57188 ("net/mlx5: Expose ifc bits for query modify header").
Other two can go through rdma-next tree.

Thanks

>
> Jason

  reply	other threads:[~2021-01-19  6:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-30 13:01 [PATCH mlx5-next 0/3] Cleanup around DEVX get/set commands Leon Romanovsky
2020-12-30 13:01 ` [PATCH mlx5-next 1/3] RDMA/mlx5: Use the correct obj_id upon DEVX TIR creation Leon Romanovsky
2020-12-30 13:01 ` [PATCH mlx5-next 2/3] net/mlx5: Expose ifc bits for query modify header Leon Romanovsky
2020-12-30 13:01 ` [PATCH mlx5-next 3/3] RDMA/mlx5: Use strict get/set operations for obj_id Leon Romanovsky
2021-01-18 20:00 ` [PATCH mlx5-next 0/3] Cleanup around DEVX get/set commands Jason Gunthorpe
2021-01-19  5:36   ` Leon Romanovsky [this message]
2021-01-19 16:50 ` 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=20210119053639.GA21258@unreal \
    --to=leon@kernel.org \
    --cc=dledford@redhat.com \
    --cc=jgg@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=saeedm@nvidia.com \
    --cc=yishaih@mellanox.com \
    --cc=yishaih@nvidia.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