From: patchwork-bot+netdevbpf@kernel.org
To: Jeremy Kerr <jk@codeconstruct.com.au>
Cc: matt@codeconstruct.com.au, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, netdev@vger.kernel.org, oliver.sang@intel.com
Subject: Re: [PATCH net 0/2] net: mctp: test: minor kunit test fixes
Date: Thu, 30 Apr 2026 21:00:09 +0000 [thread overview]
Message-ID: <177758280955.3201582.307308430080438516.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260429-dev-mctp-test-fixes-v1-0-1127b7425809@codeconstruct.com.au>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 29 Apr 2026 16:21:40 +0800 you wrote:
> This series provides two fixes in the MCTP kunit tests - one exposed by
> ktr, and one found while debugging the former on different VM configs.
>
> Signed-off-by: Jeremy Kerr <jk@codeconstruct.com.au>
> ---
> Jeremy Kerr (2):
> net: mctp: test: use a zeroed struct sockaddr_mctp
> net: mctp: test: Use dev_direct_xmit for TX to our test device
>
> [...]
Here is the summary with links:
- [net,1/2] net: mctp: test: use a zeroed struct sockaddr_mctp
https://git.kernel.org/netdev/net/c/18ed60e33e6c
- [net,2/2] net: mctp: test: Use dev_direct_xmit for TX to our test device
https://git.kernel.org/netdev/net/c/768729710641
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-04-30 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 8:21 [PATCH net 0/2] net: mctp: test: minor kunit test fixes Jeremy Kerr
2026-04-29 8:21 ` [PATCH net 1/2] net: mctp: test: use a zeroed struct sockaddr_mctp Jeremy Kerr
2026-04-29 8:21 ` [PATCH net 2/2] net: mctp: test: Use dev_direct_xmit for TX to our test device Jeremy Kerr
2026-04-30 17:15 ` [PATCH net 0/2] net: mctp: test: minor kunit test fixes Simon Horman
2026-04-30 21: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=177758280955.3201582.307308430080438516.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jk@codeconstruct.com.au \
--cc=kuba@kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
--cc=oliver.sang@intel.com \
--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 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.