netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yijing Zeng <zengyijing19900106@gmail.com>
Cc: netdev@vger.kernel.org, stephen@networkplumber.org,
	me@pmachata.org, kuba@kernel.org, yijingzeng@meta.com
Subject: Re: [PATCH v2] dcb: fix tc-maxrate unit conversions
Date: Thu, 16 Oct 2025 22:10:09 +0000	[thread overview]
Message-ID: <176065260902.1923966.15696761521517630320.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251011222829.25295-1-zengyijing19900106@gmail.com>

Hello:

This patch was applied to iproute2/iproute2.git (main)
by Stephen Hemminger <stephen@networkplumber.org>:

On Sat, 11 Oct 2025 15:25:24 -0700 you wrote:
> From: Yijing Zeng <yijingzeng@meta.com>
> 
> The ieee_maxrate UAPI is defined as kbps, but dcb_maxrate uses Bps.
> This fix patch converts Bps to kbps for parse by dividing 125,
> and convert kbps to Bps for print_rate() by multiplying 125.
> 
> Fixes: 117939d9bd89 ("dcb: Add a subtool for the DCB maxrate object")
> Signed-off-by: Yijing Zeng <yijingzeng@meta.com>
> 
> [...]

Here is the summary with links:
  - [v2] dcb: fix tc-maxrate unit conversions
    https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=af33b4800265

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2025-10-16 22:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-08  3:16 [PATCH] dcb: fix tc-maxrate unit conversions Yijing Zeng
2025-10-09 16:01 ` Petr Machata
2025-10-11 22:25 ` [PATCH v2] " Yijing Zeng
2025-10-16 22:10   ` 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=176065260902.1923966.15696761521517630320.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=kuba@kernel.org \
    --cc=me@pmachata.org \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    --cc=yijingzeng@meta.com \
    --cc=zengyijing19900106@gmail.com \
    /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).