From: patchwork-bot+netdevbpf@kernel.org
To: Tao Cui <cui.tao@linux.dev>
Cc: dsahern@kernel.org, leonro@nvidia.com,
linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
cuitao@kylinos.cn
Subject: Re: [PATCH iproute2-next v7 0/2] rdma: display resource limits in curr/max format
Date: Thu, 16 Jul 2026 20:50:07 +0000 [thread overview]
Message-ID: <178423500714.1415745.12369872060313952704.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260716115237.1859633-1-cui.tao@linux.dev>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Thu, 16 Jul 2026 19:52:35 +0800 you wrote:
> From: Tao Cui <cuitao@kylinos.cn>
>
> This series adds support for displaying RDMA device resource limits in
> curr/max format in the rdma tool, building on the kernel uapi attribute
> RDMA_NLDEV_ATTR_RES_SUMMARY_ENTRY_MAX which has landed in linux-next
> (kernel commit 5911f6d6e7cc [1]).
>
> [...]
Here is the summary with links:
- [iproute2-next,v7,1/2] rdma: update uapi headers
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=39eb3a40d967
- [iproute2-next,v7,2/2] rdma: display resource limits in curr/max format
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=35a237091c24
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:[~2026-07-16 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 11:52 [PATCH iproute2-next v7 0/2] rdma: display resource limits in curr/max format Tao Cui
2026-07-16 11:52 ` [PATCH iproute2-next v7 1/2] rdma: update uapi headers Tao Cui
2026-07-16 11:52 ` [PATCH iproute2-next v7 2/2] rdma: display resource limits in curr/max format Tao Cui
2026-07-16 20:50 ` 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=178423500714.1415745.12369872060313952704.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=cui.tao@linux.dev \
--cc=cuitao@kylinos.cn \
--cc=dsahern@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.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.