From: Leon Romanovsky <leon@kernel.org>
To: Junxian Huang <huangjunxian6@hisilicon.com>
Cc: jgg@ziepe.ca, linux-rdma@vger.kernel.org, linuxarm@huawei.com,
linux-kernel@vger.kernel.org, David Ahern <dsahern@gmail.com>,
Stephen Hemminger <stephen@networkplumber.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH 0/2] rdma: Support dumping SRQ resource in raw format
Date: Mon, 2 Oct 2023 14:16:31 +0300 [thread overview]
Message-ID: <20231002111631.GD7059@unreal> (raw)
In-Reply-To: <20230928063202.1435527-1-huangjunxian6@hisilicon.com>
On Thu, Sep 28, 2023 at 02:32:00PM +0800, Junxian Huang wrote:
> This patchset adds support to dump SRQ resource in raw format with
> rdmatool. The corresponding kernel commit is aebf8145e11a
> ("RDMA/core: Add support to dump SRQ resource in RAW format")
>
> Junxian Huang (1):
> rdma: Update uapi headers
>
> wenglianfa (1):
> rdma: Add support to dump SRQ resource in raw format
>
> rdma/include/uapi/rdma/rdma_netlink.h | 2 ++
> rdma/res-srq.c | 17 ++++++++++++++++-
> rdma/res.h | 2 ++
> 3 files changed, 20 insertions(+), 1 deletion(-)
rdmatool is part of iproute2 suite and as such To, Cc and Subject should
follow that suite rules. You need to add David to "TO", add Stephen and
netdev and add target (iproute2-next) for this patches.
See this randomly chosen series as an example.
https://lore.kernel.org/netdev/20211014075358.239708-1-markzhang@nvidia.com/
or latest one
https://lore.kernel.org/netdev/20231002104349.971927-1-tariqt@nvidia.com/T/#m7ef8e4ce275052d428b4f13ad9f3b41a4bf5d46b
Thanks
>
> --
> 2.30.0
>
next parent reply other threads:[~2023-10-02 11:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230928063202.1435527-1-huangjunxian6@hisilicon.com>
2023-10-02 11:16 ` Leon Romanovsky [this message]
2023-10-07 3:43 ` [PATCH 0/2] rdma: Support dumping SRQ resource in raw format Junxian Huang
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=20231002111631.GD7059@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 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).