From: Petr Machata <petrm@nvidia.com>
To: Patrisious Haddad <phaddad@nvidia.com>
Cc: David Ahern <dsahern@gmail.com>, <jgg@ziepe.ca>,
<leon@kernel.org>, <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 v2 iproute2-next 2/3] rdma: Add an option to set privileged QKEY parameter
Date: Wed, 25 Oct 2023 10:34:50 +0200 [thread overview]
Message-ID: <87r0lj5cad.fsf@nvidia.com> (raw)
In-Reply-To: <d97b7d9c-e5e4-8352-d805-e7ebcbad80e3@nvidia.com>
Patrisious Haddad <phaddad@nvidia.com> writes:
> On 10/24/2023 8:02 PM, David Ahern wrote:
>
>>> +
>>> + print_color_on_off(PRINT_ANY, COLOR_NONE, "privileged-qkey",
>>> + "privileged-qkey %s ", pqkey_mode);
>>> +
>>> + }
>>> +
>>> if (tb[RDMA_NLDEV_SYS_ATTR_COPY_ON_FORK])
>>> cof = mnl_attr_get_u8(tb[RDMA_NLDEV_SYS_ATTR_COPY_ON_FORK]);
>>>
>> keep Petr's reviewed-by tag on the respin.
>
> will do, just making sure I understand "the respin" , you mean when I
> re-send it ?
Yes, to send a new version with fixes.
next prev parent reply other threads:[~2023-10-25 8:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 11:22 [PATCH v2 iproute2-next 0/3] Add support to set privileged qkey parameter Patrisious Haddad
2023-10-23 11:22 ` [PATCH v2 iproute2-next 1/3] rdma: update uapi headers Patrisious Haddad
2023-10-23 11:22 ` [PATCH v2 iproute2-next 2/3] rdma: Add an option to set privileged QKEY parameter Patrisious Haddad
2023-10-24 15:34 ` Petr Machata
2023-10-24 17:02 ` David Ahern
2023-10-25 6:26 ` Patrisious Haddad
2023-10-25 8:34 ` Petr Machata [this message]
2023-10-25 8:25 ` Petr Machata
2023-10-23 11:22 ` [PATCH v2 iproute2-next 3/3] rdma: Adjust man page for rdma system set privileged_qkey command Patrisious Haddad
2023-10-24 16:09 ` Petr Machata
2023-10-24 17:04 ` David Ahern
2023-10-25 6:10 ` Patrisious Haddad
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=87r0lj5cad.fsf@nvidia.com \
--to=petrm@nvidia.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.