From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: edumazet@google.com, netdev@vger.kernel.org, davem@davemloft.net,
pabeni@redhat.com, jhs@mojatatu.com, xiyou.wangcong@gmail.com,
jiri@resnulli.us, shuah@kernel.org, karansanghvi98@gmail.com,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net] selftests: tc-testing: reduce rshift value
Date: Sat, 04 Jan 2025 17:00:32 +0000 [thread overview]
Message-ID: <173601003258.2470506.15418875241946232841.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250103182458.1213486-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 3 Jan 2025 10:24:58 -0800 you wrote:
> After previous change rshift >= 32 is no longer allowed.
> Modify the test to use 31, the test doesn't seem to send
> any traffic so the exact value shouldn't matter.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> CC: jhs@mojatatu.com
> CC: xiyou.wangcong@gmail.com
> CC: jiri@resnulli.us
> CC: shuah@kernel.org
> CC: karansanghvi98@gmail.com
> CC: linux-kselftest@vger.kernel.org
>
> [...]
Here is the summary with links:
- [net] selftests: tc-testing: reduce rshift value
https://git.kernel.org/netdev/net/c/e95274dfe864
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-01-04 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 10:45 [PATCH net] net_sched: cls_flow: validate TCA_FLOW_RSHIFT attribute Eric Dumazet
2025-01-03 18:24 ` [PATCH net] selftests: tc-testing: reduce rshift value Jakub Kicinski
2025-01-03 18:35 ` Eric Dumazet
2025-01-04 17:00 ` patchwork-bot+netdevbpf [this message]
2025-01-04 17:00 ` [PATCH net] net_sched: cls_flow: validate TCA_FLOW_RSHIFT attribute patchwork-bot+netdevbpf
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=173601003258.2470506.15418875241946232841.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=karansanghvi98@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--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 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).