From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>
Cc: linux-rdma@vger.kernel.org,
Michael Guralnik <michaelgur@nvidia.com>,
Or Har-Toov <ohartoov@nvidia.com>,
Leon Romanovsky <leon@kernel.org>
Subject: Re: [PATCH rdma-next v2 0/3] Rewrite mlx3 mkeys logic
Date: Mon, 08 Apr 2024 13:35:24 +0300 [thread overview]
Message-ID: <171257252420.54501.7225632184008065959.b4-ty@kernel.org> (raw)
In-Reply-To: <cover.1712140377.git.leon@kernel.org>
On Wed, 03 Apr 2024 13:35:58 +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> This is rewrote version of [1].
>
> [1] https://lore.kernel.org/all/cover.1706433934.git.leon@kernel.org
>
> Thanks
>
> [...]
Applied, thanks!
[1/3] RDMA/mlx5: Uncacheable mkey has neither rb_key or cache_ent
https://git.kernel.org/rdma/rdma/c/0611a8e8b475fc
[2/3] RDMA/mlx5: Change check for cacheable mkeys
https://git.kernel.org/rdma/rdma/c/8c1185fef68cc6
[3/3] RDMA/mlx5: Adding remote atomic access flag to updatable flags
https://git.kernel.org/rdma/rdma/c/2ca7e93bc963d9
Best regards,
--
Leon Romanovsky <leon@kernel.org>
prev parent reply other threads:[~2024-04-08 10:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 10:35 [PATCH rdma-next v2 0/3] Rewrite mlx3 mkeys logic Leon Romanovsky
2024-04-03 10:35 ` [PATCH rdma-next v2 1/3] RDMA/mlx5: Uncacheable mkey has neither rb_key or cache_ent Leon Romanovsky
2024-04-03 10:36 ` [PATCH rdma-next v2 2/3] RDMA/mlx5: Change check for cacheable mkeys Leon Romanovsky
2024-04-03 10:36 ` [PATCH rdma-next v2 3/3] RDMA/mlx5: Adding remote atomic access flag to updatable flags Leon Romanovsky
2024-04-03 10:44 ` [PATCH rdma-next v2 0/3] Rewrite mlx3 mkeys logic Leon Romanovsky
2024-04-08 10:35 ` 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=171257252420.54501.7225632184008065959.b4-ty@kernel.org \
--to=leon@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=michaelgur@nvidia.com \
--cc=ohartoov@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