From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
shuah@kernel.org, almasrymina@google.com, sdf@fomichev.me,
joe@dama.to, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/5] selftests: drv-net: ncdevmem: fix error paths
Date: Wed, 27 Aug 2025 01:00:27 +0000 [thread overview]
Message-ID: <175625642798.155051.9564153907183706947.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250825180447.2252977-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 25 Aug 2025 11:04:42 -0700 you wrote:
> Make ncdevmem clean up after itself. While at it make sure it sets
> HDS threshold to 0 automatically.
>
> v2: rework patch 4 into separate patches 4 and 5
> v1: https://lore.kernel.org/20250822200052.1675613-1-kuba@kernel.org
>
> Jakub Kicinski (5):
> selftests: drv-net: ncdevmem: remove use of error()
> selftests: drv-net: ncdevmem: save IDs of flow rules we added
> selftests: drv-net: ncdevmem: restore old channel config
> selftests: drv-net: ncdevmem: restore original HDS setting before
> exiting
> selftests: drv-net: ncdevmem: explicitly set HDS threshold to 0
>
> [...]
Here is the summary with links:
- [net-next,v2,1/5] selftests: drv-net: ncdevmem: remove use of error()
https://git.kernel.org/netdev/net-next/c/6925f6171439
- [net-next,v2,2/5] selftests: drv-net: ncdevmem: save IDs of flow rules we added
https://git.kernel.org/netdev/net-next/c/6d04b36c73fd
- [net-next,v2,3/5] selftests: drv-net: ncdevmem: restore old channel config
https://git.kernel.org/netdev/net-next/c/b9f4f9529828
- [net-next,v2,4/5] selftests: drv-net: ncdevmem: restore original HDS setting before exiting
https://git.kernel.org/netdev/net-next/c/6351fadbd5bb
- [net-next,v2,5/5] selftests: drv-net: ncdevmem: explicitly set HDS threshold to 0
https://git.kernel.org/netdev/net-next/c/a9d533fbba0d
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:[~2025-08-27 1:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 18:04 [PATCH net-next v2 0/5] selftests: drv-net: ncdevmem: fix error paths Jakub Kicinski
2025-08-25 18:04 ` [PATCH net-next v2 1/5] selftests: drv-net: ncdevmem: remove use of error() Jakub Kicinski
2025-08-25 18:04 ` [PATCH net-next v2 2/5] selftests: drv-net: ncdevmem: save IDs of flow rules we added Jakub Kicinski
2025-08-25 18:04 ` [PATCH net-next v2 3/5] selftests: drv-net: ncdevmem: restore old channel config Jakub Kicinski
2025-08-25 18:04 ` [PATCH net-next v2 4/5] selftests: drv-net: ncdevmem: restore original HDS setting before exiting Jakub Kicinski
2025-08-25 19:53 ` Stanislav Fomichev
2025-08-25 18:04 ` [PATCH net-next v2 5/5] selftests: drv-net: ncdevmem: explicitly set HDS threshold to 0 Jakub Kicinski
2025-08-25 19:54 ` Stanislav Fomichev
2025-08-27 1:00 ` 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=175625642798.155051.9564153907183706947.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=almasrymina@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=joe@dama.to \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=shuah@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).