From: Leon Romanovsky <leonro@nvidia.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Edward Srouji <edwards@nvidia.com>, <linux-rdma@vger.kernel.org>,
"Maor Gottlieb" <maorg@nvidia.com>,
Mark Zhang <markzhang@nvidia.com>,
"Michael Guralnik" <michaelgur@nvidia.com>,
Or Har-Toov <ohartoov@nvidia.com>,
"Tamar Mashiah" <tmashiah@nvidia.com>,
Yishai Hadas <yishaih@nvidia.com>
Subject: Re: [PATCH rdma-next v1 0/6] Collection of mlx5_ib fixes
Date: Wed, 31 Jan 2024 11:18:30 +0200 [thread overview]
Message-ID: <20240131091830.GD71813@unreal> (raw)
In-Reply-To: <cover.1706433934.git.leon@kernel.org>
On Sun, Jan 28, 2024 at 11:29:10AM +0200, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
<...>
> Leon Romanovsky (1):
> RDMA/mlx5: Fix fortify source warning while accessing Eth segment
>
> Mark Zhang (1):
> IB/mlx5: Don't expose debugfs entries for RRoCE general parameters if
> not supported
>
> Yishai Hadas (1):
> RDMA/mlx5: Relax DEVX access upon modify commands
Applied these patches to -rc.
>
> Or Har-Toov (3):
> RDMA/mlx5: Uncacheable mkey has neither rb_key or cache_ent
> RDMA/mlx5: Change check for cacheable user mkeys
> RDMA/mlx5: Adding remote atomic access flag to updatable flags
These patches under discussion and will be needed to resend anyway.
Thanks
prev parent reply other threads:[~2024-01-31 9:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-28 9:29 [PATCH rdma-next v1 0/6] Collection of mlx5_ib fixes Leon Romanovsky
2024-01-28 9:29 ` [PATCH rdma-next v1 1/6] RDMA/mlx5: Fix fortify source warning while accessing Eth segment Leon Romanovsky
2024-01-28 9:29 ` [PATCH rdma-next v1 2/6] IB/mlx5: Don't expose debugfs entries for RRoCE general parameters if not supported Leon Romanovsky
2024-01-28 9:29 ` [PATCH rdma-next v1 3/6] RDMA/mlx5: Relax DEVX access upon modify commands Leon Romanovsky
2024-01-28 9:29 ` [PATCH rdma-next v1 4/6] RDMA/mlx5: Uncacheable mkey has neither rb_key or cache_ent Leon Romanovsky
2024-01-28 9:29 ` [PATCH rdma-next v1 5/6] RDMA/mlx5: Change check for cacheable user mkeys Leon Romanovsky
2024-01-29 17:52 ` Jason Gunthorpe
2024-01-30 13:47 ` Leon Romanovsky
2024-01-28 9:29 ` [PATCH rdma-next v1 6/6] RDMA/mlx5: Adding remote atomic access flag to updatable flags Leon Romanovsky
2024-01-31 9:16 ` (subset) [PATCH rdma-next v1 0/6] Collection of mlx5_ib fixes Leon Romanovsky
2024-01-31 9:18 ` 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=20240131091830.GD71813@unreal \
--to=leonro@nvidia.com \
--cc=edwards@nvidia.com \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=maorg@nvidia.com \
--cc=markzhang@nvidia.com \
--cc=michaelgur@nvidia.com \
--cc=ohartoov@nvidia.com \
--cc=tmashiah@nvidia.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;
as well as URLs for NNTP newsgroup(s).