From: Leon Romanovsky <leon@kernel.org>
To: Patrisious Haddad <phaddad@nvidia.com>
Cc: jgg@ziepe.ca, dsahern@gmail.com, stephen@networkplumber.org,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
linuxarm@huawei.com, linux-kernel@vger.kernel.org,
huangjunxian6@hisilicon.com, michaelgur@nvidia.com
Subject: Re: [RFC iproute2-next 0/3] Add support to set privileged qkey parameter
Date: Thu, 19 Oct 2023 09:37:23 +0300 [thread overview]
Message-ID: <20231019063723.GJ5392@unreal> (raw)
In-Reply-To: <20231016063103.19872-1-phaddad@nvidia.com>
On Mon, Oct 16, 2023 at 09:31:00AM +0300, Patrisious Haddad wrote:
> This patchset adds support to enable or disable privileged QKEY.
> When enabled, non-privileged users will be allowed to specify a controlled QKEY.
> The corresponding kernel commit is yet to be merged so currently there
> is no hash but the commit name is
> ("RDMA/core: Add support to set privileged qkey parameter")
>
> All the information regarding the added parameter and its usage are included
> in the commits below and the edited man page.
>
> Patrisious Haddad (3):
> rdma: update uapi headers
Kernel patch was accepted https://lore.kernel.org/all/169769714759.2016184.7321591466660624597.b4-ty@kernel.org/
Please resend the series with right "rdma: update uapi headers" patch.
Thanks
prev parent reply other threads:[~2023-10-19 6:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 6:31 [RFC iproute2-next 0/3] Add support to set privileged qkey parameter Patrisious Haddad
2023-10-16 6:31 ` [RFC iproute2-next 1/3] rdma: update uapi headers Patrisious Haddad
2023-10-16 6:31 ` [RFC iproute2-next 2/3] rdma: Add an option to set privileged QKEY parameter Patrisious Haddad
2023-10-16 6:31 ` [RFC iproute2-next 3/3] rdma: Adjust man page for rdma system set privileged_qkey command Patrisious Haddad
2023-10-19 6:37 ` 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=20231019063723.GJ5392@unreal \
--to=leon@kernel.org \
--cc=dsahern@gmail.com \
--cc=huangjunxian6@hisilicon.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=michaelgur@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=phaddad@nvidia.com \
--cc=stephen@networkplumber.org \
/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).