From: David Ahern <dsahern@kernel.org>
To: Tao Cui <cui.tao@linux.dev>, leonro@nvidia.com
Cc: linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
Tao Cui <cuitao@kylinos.cn>
Subject: Re: [PATCH iproute2-next v3] rdma: display resource limits in curr/max format
Date: Mon, 29 Jun 2026 07:52:35 -0600 [thread overview]
Message-ID: <897088ee-7aea-4c76-8c4d-9d5fcb621a58@kernel.org> (raw)
In-Reply-To: <0892f5e8-7ca4-4efc-a002-8c1ed244b18e@linux.dev>
On 6/28/26 5:55 PM, Tao Cui wrote:
> If you'd prefer, I can also hold this iproute2 patch until the kernel
> side has landed, so the uapi is already in tree when it goes in. Happy
> to do whichever you think is best.
That is the request - resend after it lands with a reference to the
patch set.
prev parent reply other threads:[~2026-06-29 13:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 0:53 [PATCH iproute2-next v3] rdma: display resource limits in curr/max format Tao Cui
2026-06-28 17:22 ` David Ahern
2026-06-28 23:55 ` Tao Cui
2026-06-29 13:52 ` David Ahern [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=897088ee-7aea-4c76-8c4d-9d5fcb621a58@kernel.org \
--to=dsahern@kernel.org \
--cc=cui.tao@linux.dev \
--cc=cuitao@kylinos.cn \
--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