From: patchwork-bot+netdevbpf@kernel.org
To: Gal Pressman <gal@nvidia.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, andrew+netdev@lunn.ch, netdev@vger.kernel.org,
shuah@kernel.org, willemb@google.com, petrm@nvidia.com,
lixiaoyan@google.com, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net v2 0/2] selftests: Couple of fixes in Toeplitz RPS cases
Date: Wed, 14 Jan 2026 03:20:08 +0000 [thread overview]
Message-ID: <176836080865.2569860.17335295751025998084.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260112173715.384843-1-gal@nvidia.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 12 Jan 2026 19:37:13 +0200 you wrote:
> Fix a couple of bugs in the RPS cases of the Toeplitz selftest.
>
> Changelog -
> v1->v2: https://lore.kernel.org/all/20260111171658.179286-1-gal@nvidia.com/
> * Use a single mask variable in the second patch (Willem).
>
> Gal Pressman (2):
> selftests: drv-net: fix RPS mask handling in toeplitz test
> selftests: drv-net: fix RPS mask handling for high CPU numbers
>
> [...]
Here is the summary with links:
- [net,v2,1/2] selftests: drv-net: fix RPS mask handling in toeplitz test
https://git.kernel.org/netdev/net/c/9d48c62f6b4e
- [net,v2,2/2] selftests: drv-net: fix RPS mask handling for high CPU numbers
https://git.kernel.org/netdev/net/c/cf055f8c0004
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-01-14 3:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 17:37 [PATCH net v2 0/2] selftests: Couple of fixes in Toeplitz RPS cases Gal Pressman
2026-01-12 17:37 ` [PATCH net v2 1/2] selftests: drv-net: fix RPS mask handling in toeplitz test Gal Pressman
2026-01-12 17:37 ` [PATCH net v2 2/2] selftests: drv-net: fix RPS mask handling for high CPU numbers Gal Pressman
2026-01-14 3: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=176836080865.2569860.17335295751025998084.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lixiaoyan@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=shuah@kernel.org \
--cc=willemb@google.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