netdev - Re: [PATCH net-next v2] net: mctp: test: move TX packetqueue from dst to dev

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: 
 <176462640879.2561615.15924092267906413026.git-patchwork-notify@kernel.org>
Date: Mon, 01 Dec 2025 22:00:08 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Jeremy Kerr <jk@...econstruct.com.au>
Cc: matt@...econstruct.com.au, davem@...emloft.net, edumazet@...gle.com,
 kuba@...nel.org, pabeni@...hat.com, horms@...nel.org, netdev@...r.kernel.org
Subject: Re: [PATCH net-next v2] net: mctp: test: move TX packetqueue from dst
 to dev

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:

On Wed, 26 Nov 2025 16:48:54 +0800 you wrote:
> To capture TX packets during a test, we are currently intercepting the
> dst->output with an implementation that adds the transmitted packet to
> a skb queue attached to the test-specific mock dst. The netdev itself is
> not involved in the test TX path.
> 
> Instead, we can just use our test device to stash TXed packets for later
> inspection by the test. This means we can include the actual
> mctp_dst_output() implementation in the test (by setting dst.output in
> the test case), and don't need to be creating fake dst objects, or their
> corresponding skb queues.
> 
> [...]

Here is the summary with links:
  - [net-next,v2] net: mctp: test: move TX packetqueue from dst to dev
    https://git.kernel.org/netdev/net-next/c/6ab578739a4c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html