From: patchwork-bot+netdevbpf@kernel.org
To: James Lee <james@codeconstruct.com.au>
Cc: jk@codeconstruct.com.au, matt@codeconstruct.com.au,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, kees@kernel.org,
gustavoars@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/7] net: mctp: usblib: Increase coverage of kunit testing
Date: Tue, 20 Oct 2026 21:30:13 +0000 [thread overview]
Message-ID: <179253181301.220085.14897480542454867780.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261014-dev-mctp-usb-lib-test-v3-0-ee5bc3ea1db1@codeconstruct.com.au>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 14 Oct 2026 12:47:30 +0800 you wrote:
> Current usblib tests only check receipt of a limited combination of
> packets lengths.
>
> Added tests of receiving packets with invalid fields, and more complex
> packet spanning. Also created tests for transmitting packets, covering
> most code, except for mctp_usblib_tx_cancel() and allocation failures.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/7] net: mctp: usblib: Add to parameterized kunit tests.
https://git.kernel.org/netdev/net-next/c/acfb9c263d70
- [net-next,v3,2/7] net: mctp: usblib: Add test for splits inside headers
https://git.kernel.org/netdev/net-next/c/21e1d4515755
- [net-next,v3,3/7] net: mctp: usblib: Add tests of invalid headers
https://git.kernel.org/netdev/net-next/c/c0a372f72972
- [net-next,v3,4/7] net: mctp: usblib: Complete rx tests
https://git.kernel.org/netdev/net-next/c/40e59c00ae21
- [net-next,v3,5/7] net: mctp: usblib: Simplify allocation logic in mctp_usblib_test_rx_init
https://git.kernel.org/netdev/net-next/c/77cb5c6b3464
- [net-next,v3,6/7] net: mctp: usblib: Add initial kunit tx tests
https://git.kernel.org/netdev/net-next/c/1e12f734afc1
- [net-next,v3,7/7] net: mctp: usblib: Add test for failing append
https://git.kernel.org/netdev/net-next/c/9e061caa3bdd
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-10-20 21:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 4:47 [PATCH net-next v3 0/7] net: mctp: usblib: Increase coverage of kunit testing James Lee
2026-10-14 4:47 ` [PATCH net-next v3 1/7] net: mctp: usblib: Add to parameterized kunit tests James Lee
2026-10-14 4:47 ` [PATCH net-next v3 2/7] net: mctp: usblib: Add test for splits inside headers James Lee
2026-10-14 4:47 ` [PATCH net-next v3 3/7] net: mctp: usblib: Add tests of invalid headers James Lee
2026-10-14 4:47 ` [PATCH net-next v3 4/7] net: mctp: usblib: Complete rx tests James Lee
2026-10-14 4:47 ` [PATCH net-next v3 5/7] net: mctp: usblib: Simplify allocation logic in mctp_usblib_test_rx_init James Lee
2026-10-14 4:47 ` [PATCH net-next v3 6/7] net: mctp: usblib: Add initial kunit tx tests James Lee
2026-10-14 4:47 ` [PATCH net-next v3 7/7] net: mctp: usblib: Add test for failing append James Lee
2026-10-20 21:30 ` 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=179253181301.220085.14897480542454867780.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=gustavoars@kernel.org \
--cc=james@codeconstruct.com.au \
--cc=jk@codeconstruct.com.au \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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