From: David Ahern <dsahern@gmail.com>
To: Mark Bloch <mbloch@nvidia.com>, Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, Carolina Jubran <cjubran@nvidia.com>
Subject: Re: [RFC PATCH iproute2-next] devlink: Add support for 'tc-bw' attribute in devlink-rate
Date: Wed, 25 Jun 2025 19:42:23 -0600 [thread overview]
Message-ID: <da9eb3d8-a2ce-4042-ac2f-9d0a0cb84fbe@gmail.com> (raw)
In-Reply-To: <20250625182545.86994-1-mbloch@nvidia.com>
On 6/25/25 12:25 PM, Mark Bloch wrote:
>
> I've incldued the header file changes in this patch for ease of use.
uapi updates should be a separate patch.
next prev parent reply other threads:[~2025-06-26 1:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 18:25 [RFC PATCH iproute2-next] devlink: Add support for 'tc-bw' attribute in devlink-rate Mark Bloch
2025-06-26 1:42 ` David Ahern [this message]
2025-06-27 13:12 ` Mark Bloch
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=da9eb3d8-a2ce-4042-ac2f-9d0a0cb84fbe@gmail.com \
--to=dsahern@gmail.com \
--cc=cjubran@nvidia.com \
--cc=kuba@kernel.org \
--cc=mbloch@nvidia.com \
--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 NNTP newsgroup(s).