From: patchwork-bot+netdevbpf@kernel.org
To: Junxian Huang <huangjunxian6@hisilicon.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
Subject: Re: [PATCH v2 iproute2-next 0/2] rdma: Support dumping SRQ resource in raw format
Date: Mon, 16 Oct 2023 16:20:27 +0000 [thread overview]
Message-ID: <169747322756.5359.10248022521412902967.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231010075526.3860869-1-huangjunxian6@hisilicon.com>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Tue, 10 Oct 2023 15:55:24 +0800 you 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")
>
> v2 adds the missing change in res_srq_idx_parse_cb().
>
> Junxian Huang (1):
> rdma: Update uapi headers
>
> [...]
Here is the summary with links:
- [v2,iproute2-next,1/2] rdma: Update uapi headers
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=cd4315de422e
- [v2,iproute2-next,2/2] rdma: Add support to dump SRQ resource in raw format
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=07bfa4482d49
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-16 16:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 7:55 [PATCH v2 iproute2-next 0/2] rdma: Support dumping SRQ resource in raw format Junxian Huang
2023-10-10 7:55 ` [PATCH v2 iproute2-next 1/2] rdma: Update uapi headers Junxian Huang
2023-10-15 8:14 ` Leon Romanovsky
2023-10-10 7:55 ` [PATCH v2 iproute2-next 2/2] rdma: Add support to dump SRQ resource in raw format Junxian Huang
2023-10-15 8:15 ` Leon Romanovsky
2023-10-16 3:54 ` David Ahern
2023-10-16 6:31 ` Leon Romanovsky
2023-10-16 16:20 ` 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=169747322756.5359.10248022521412902967.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=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.