From: patchwork-bot+netdevbpf@kernel.org
To: Patrisious Haddad <phaddad@nvidia.com>
Cc: leon@kernel.org, dsahern@gmail.com, stephen@networkplumber.org,
netdev@vger.kernel.org, jgg@nvidia.com,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH iproute2-next 0/2] Add optional-counters binding support
Date: Mon, 24 Mar 2025 02:50:33 +0000 [thread overview]
Message-ID: <174278463329.3212931.9680954634489028299.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250319082529.287168-1-phaddad@nvidia.com>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Wed, 19 Mar 2025 10:25:24 +0200 you wrote:
> Add optional-counters binding support together with new packets/bytes
> counters. Previously optional-counters were on a per link basis, this
> series allows users to bind optional-counters to a specific counter,
> which allows tracking optional-counter over a specific QP group.
>
> The support is added for both binding modes, automatic and manual,
> in both cases the bound optional counters are those that are currently
> configured over the link when trying to bind the QP.
>
> [...]
Here is the summary with links:
- [iproute2-next,1/2] rdma: update uapi headers
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=85860c7dce2c
- [iproute2-next,2/2] rdma: Add optional-counter option to rdma stat bind commands
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=a03f40534f6c
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:[~2025-03-24 2:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
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
2025-03-19 8:25 ` [PATCH iproute2-next 2/2] rdma: Add optional-counter option to rdma stat bind commands Patrisious Haddad
2025-03-24 2: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=174278463329.3212931.9680954634489028299.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dsahern@gmail.com \
--cc=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=phaddad@nvidia.com \
--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.