From: patchwork-bot+netdevbpf@kernel.org
To: Patrisious Haddad <phaddad@nvidia.com>
Cc: jgg@ziepe.ca, leon@kernel.org, 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: [PATCH v3 iproute2-next 0/3] Add support to set privileged qkey parameter
Date: Thu, 26 Oct 2023 00:10:24 +0000 [thread overview]
Message-ID: <169827902428.6163.13738163996032599729.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231025123102.27784-1-phaddad@nvidia.com>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Wed, 25 Oct 2023 15:30:59 +0300 you 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 36ce80759f8c
> ("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.
>
> [...]
Here is the summary with links:
- [v3,iproute2-next,1/3] rdma: update uapi headers
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=bbcebb2ea76b
- [v3,iproute2-next,2/3] rdma: Add an option to set privileged QKEY parameter
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=21180a7ac40a
- [v3,iproute2-next,3/3] rdma: Adjust man page for rdma system set privileged-qkey command
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=ecea0c2a7bba
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-10-26 0:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 12:30 [PATCH v3 iproute2-next 0/3] Add support to set privileged qkey parameter Patrisious Haddad
2023-10-25 12:31 ` [PATCH v3 iproute2-next 1/3] rdma: update uapi headers Patrisious Haddad
2023-10-25 12:31 ` [PATCH v3 iproute2-next 2/3] rdma: Add an option to set privileged QKEY parameter Patrisious Haddad
2023-10-25 12:31 ` [PATCH v3 iproute2-next 3/3] rdma: Adjust man page for rdma system set privileged-qkey command Patrisious Haddad
2023-10-26 0:10 ` patchwork-bot+netdevbpf [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=169827902428.6163.13738163996032599729.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dsahern@gmail.com \
--cc=huangjunxian6@hisilicon.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--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).