All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Victor Nogueira <victor@mojatatu.com>
Cc: jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
	kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
	jay.vosburgh@canonical.com
Subject: Re: [PATCH net-next] selftests/tc-testing: Adapt tc police action tests for Gb rounding changes
Date: Mon, 15 Sep 2025 23:20:07 +0000	[thread overview]
Message-ID: <175797840700.158095.11873406828281486126.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250912154616.67489-1-victor@mojatatu.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Fri, 12 Sep 2025 12:46:16 -0300 you wrote:
> For the tc police action, iproute2 rounds up mtu and burst sizes to a
> higher order representation. For example, if the user specifies the default
> mtu for a police action instance (4294967295 bytes), iproute2 will output
> it as 4096Mb when this action instance is dumped. After Jay's changes [1],
> iproute2 will round up to Gb, so 4096Mb becomes 4Gb. With that in mind,
> fix police's tc test output so that it works both with the current
> iproute2 version and Jay's.
> 
> [...]

Here is the summary with links:
  - [net-next] selftests/tc-testing: Adapt tc police action tests for Gb rounding changes
    https://git.kernel.org/netdev/net-next/c/b7df2e7eaef7

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



      parent reply	other threads:[~2025-09-15 23:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-12 15:46 [PATCH net-next] selftests/tc-testing: Adapt tc police action tests for Gb rounding changes Victor Nogueira
2025-09-14  5:06 ` Cong Wang
2025-09-15 22:14 ` Jay Vosburgh
2025-09-15 23: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=175797840700.158095.11873406828281486126.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=jay.vosburgh@canonical.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=victor@mojatatu.com \
    --cc=xiyou.wangcong@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 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.