From: Jason Gunthorpe <jgg@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Doug Ledford <dledford@redhat.com>,
Leon Romanovsky <leonro@nvidia.com>, <linux-rdma@vger.kernel.org>,
Parav Pandit <parav@nvidia.com>
Subject: Re: [PATCH rdma-next v1 0/5] Various cleanups
Date: Fri, 5 Feb 2021 13:40:38 -0400 [thread overview]
Message-ID: <20210205174038.GA954997@nvidia.com> (raw)
In-Reply-To: <20210203130133.4057329-1-leon@kernel.org>
On Wed, Feb 03, 2021 at 03:01:28PM +0200, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> Changelog:
> v1:
> * Rebase
> v0: https://lore.kernel.org/linux-rdma/20210127150010.1876121-1-leon@kernel.org
>
> Parav Pandit (5):
> IB/mlx5: Move mlx5_port_caps from mlx5_core_dev to mlx5_ib_dev
> IB/mlx5: Avoid calling query device for reading pkey table length
> IB/mlx5: Improve query port for representor port
> RDMA/core: Introduce and use API to read port immutable data
> IB/mlx5: Use rdma_for_each_port for port iteration
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2021-02-05 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 13:01 [PATCH rdma-next v1 0/5] Various cleanups Leon Romanovsky
2021-02-03 13:01 ` [PATCH rdma-next v1 1/5] IB/mlx5: Move mlx5_port_caps from mlx5_core_dev to mlx5_ib_dev Leon Romanovsky
2021-02-03 13:01 ` [PATCH rdma-next v1 2/5] IB/mlx5: Avoid calling query device for reading pkey table length Leon Romanovsky
2021-02-03 13:01 ` [PATCH rdma-next v1 3/5] IB/mlx5: Improve query port for representor port Leon Romanovsky
2021-02-03 13:01 ` [PATCH rdma-next v1 4/5] RDMA/core: Introduce and use API to read port immutable data Leon Romanovsky
2021-02-03 13:01 ` [PATCH rdma-next v1 5/5] IB/mlx5: Use rdma_for_each_port for port iteration Leon Romanovsky
2021-02-05 17:40 ` 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=20210205174038.GA954997@nvidia.com \
--to=jgg@nvidia.com \
--cc=dledford@redhat.com \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=parav@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