From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Chris Mi <cmi@nvidia.com>,
linux-rdma@vger.kernel.org, Maher Sanalla <msanalla@nvidia.com>,
Maor Gottlieb <maorg@nvidia.com>,
netdev@vger.kernel.org, Saeed Mahameed <saeedm@nvidia.com>
Subject: Re: [PATCH rdma-rc 0/3] Batch of fixes to mlx5_ib
Date: Mon, 5 Sep 2022 14:50:42 +0300 [thread overview]
Message-ID: <YxXikif2QKrUPVhN@unreal> (raw)
In-Reply-To: <cover.1661763459.git.leonro@nvidia.com>
On Mon, Aug 29, 2022 at 12:02:26PM +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> Hi,
>
> This is batch of independent fixes related to mlx5_ib driver.
>
> Thanks
>
> Chris Mi (1):
> RDMA/mlx5: Set local port to one when accessing counters
>
> Maher Sanalla (1):
> RDMA/mlx5: Rely on RoCE fw cap instead of devlink when setting profile
>
> Maor Gottlieb (1):
> RDMA/mlx5: Fix UMR cleanup on error flow of driver init
>
> drivers/infiniband/hw/mlx5/mad.c | 6 +++++
> drivers/infiniband/hw/mlx5/main.c | 2 +-
> drivers/infiniband/hw/mlx5/mlx5_ib.h | 1 +
> drivers/infiniband/hw/mlx5/umr.c | 3 +++
> .../net/ethernet/mellanox/mlx5/core/main.c | 23 +++++++++++++++++--
> include/linux/mlx5/driver.h | 19 +++++++--------
> 6 files changed, 42 insertions(+), 12 deletions(-)
Thanks, applied to rdma-rc.
>
> --
> 2.37.2
>
prev parent reply other threads:[~2022-09-05 11:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 9:02 [PATCH rdma-rc 0/3] Batch of fixes to mlx5_ib Leon Romanovsky
2022-08-29 9:02 ` [PATCH rdma-rc 1/3] RDMA/mlx5: Rely on RoCE fw cap instead of devlink when setting profile Leon Romanovsky
2022-08-29 9:02 ` [PATCH rdma-rc 2/3] RDMA/mlx5: Set local port to one when accessing counters Leon Romanovsky
2022-08-29 9:02 ` [PATCH rdma-rc 3/3] RDMA/mlx5: Fix UMR cleanup on error flow of driver init Leon Romanovsky
2022-09-05 11:50 ` Leon Romanovsky [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=YxXikif2QKrUPVhN@unreal \
--to=leon@kernel.org \
--cc=cmi@nvidia.com \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=maorg@nvidia.com \
--cc=msanalla@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@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;
as well as URLs for NNTP newsgroup(s).