From: Leon Romanovsky <leon@kernel.org>
To: Junxian Huang <huangjunxian6@hisilicon.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
Subject: Re: [PATCH iproute2-next 1/2] rdma: Update uapi headers
Date: Mon, 9 Oct 2023 11:44:49 +0300 [thread overview]
Message-ID: <20231009084449.GD5042@unreal> (raw)
In-Reply-To: <20231007035855.2273364-2-huangjunxian6@hisilicon.com>
On Sat, Oct 07, 2023 at 11:58:54AM +0800, Junxian Huang wrote:
> Update rdma_netlink.h file upto kernel commit aebf8145e11a
> ("RDMA/core: Add support to dump SRQ resource in RAW format")
>
> Signed-off-by: wenglianfa <wenglianfa@huawei.com>
> Signed-off-by: Junxian Huang <huangjunxian6@hisilicon.com>
> ---
> rdma/include/uapi/rdma/rdma_netlink.h | 2 ++
> 1 file changed, 2 insertions(+)
>
Thanks,
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
next prev parent reply other threads:[~2023-10-09 8:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 3:58 [PATCH iproute2-next 0/2] rdma: Support dumping SRQ resource in raw format Junxian Huang
2023-10-07 3:58 ` [PATCH iproute2-next 1/2] rdma: Update uapi headers Junxian Huang
2023-10-09 8:44 ` Leon Romanovsky [this message]
2023-10-07 3:58 ` [PATCH iproute2-next 2/2] rdma: Add support to dump SRQ resource in raw format Junxian Huang
2023-10-09 8:44 ` Leon Romanovsky
-- strict thread matches above, loose matches on Subject: below --
2025-03-19 8:25 [PATCH iproute2-next 0/2] Add optional-counters binding support Patrisious Haddad
2025-03-19 8:25 ` [PATCH iproute2-next 1/2] rdma: update uapi headers Patrisious Haddad
2021-04-28 11:42 [PATCH iproute2-next 0/2] Add copy-on-fork to get sys command Gal Pressman
2021-04-28 11:42 ` [PATCH iproute2-next 1/2] rdma: update uapi headers Gal Pressman
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=20231009084449.GD5042@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=netdev@vger.kernel.org \
--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.