From: patchwork-bot+netdevbpf@kernel.org
To: Leon Romanovsky <leon@kernel.org>
Cc: dsahern@gmail.com, leonro@nvidia.com, cmeiohas@nvidia.com,
jgg@nvidia.com, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH iproute2-next 0/2] Extend rdmatool to print driver QPs too
Date: Fri, 03 May 2024 15:20:28 +0000 [thread overview]
Message-ID: <171474962809.564.7254054203723498127.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1714472040.git.leonro@nvidia.com>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Tue, 30 Apr 2024 13:18:18 +0300 you wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> This series is complimentary to the kernel patches that exposed to the
> userspace the driver-specific QPs.
>
> https://lore.kernel.org/all/2607bb3ddec3cae3443c2ea19e9f700825d20a98.1713268997.git.leon@kernel.org
>
> [...]
Here is the summary with links:
- [iproute2-next,1/2] rdma: update uapi header
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=e459ea4392c4
- [iproute2-next,2/2] rdma: Add an option to display driver-specific QPs in the rdma tool
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=57d7a8fd904c
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:[~2024-05-03 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 10:18 [PATCH iproute2-next 0/2] Extend rdmatool to print driver QPs too Leon Romanovsky
2024-04-30 10:18 ` [PATCH iproute2-next 1/2] rdma: update uapi header Leon Romanovsky
2024-04-30 14:43 ` [EXTERNAL] " Subbaraya Sundeep Bhatta
2024-04-30 10:18 ` [PATCH iproute2-next 2/2] rdma: Add an option to display driver-specific QPs in the rdma tool Leon Romanovsky
2024-05-03 15: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=171474962809.564.7254054203723498127.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=cmeiohas@nvidia.com \
--cc=dsahern@gmail.com \
--cc=jgg@nvidia.com \
--cc=leon@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).