From: patchwork-bot+netdevbpf@kernel•org
To: Willem de Bruijn <willemdebruijn.kernel@gmail•com>
Cc: netdev@vger•kernel.org, davem@davemloft•net, kuba@kernel•org,
edumazet@google•com, pabeni@redhat•com,
alexander.duyck@gmail•com, fw@strlen•de, willemb@google•com
Subject: Re: [PATCH net-next v3 0/3] add skb_segment kunit coverage
Date: Wed, 11 Oct 2023 09:40:27 +0000 [thread overview]
Message-ID: <169701722775.1947.6980237139794467834.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231009144205.269931-1-willemdebruijn.kernel@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft•net>:
On Mon, 9 Oct 2023 10:41:50 -0400 you wrote:
> From: Willem de Bruijn <willemb@google•com>
>
> As discussed at netconf last week. Some kernel code is exercised in
> many different ways. skb_segment is a prime example. This ~350 line
> function has 49 different patches in git blame with 28 different
> authors.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/3] net: add skb_segment kunit test
https://git.kernel.org/netdev/net-next/c/b3098d32ed6e
- [net-next,v3,2/3] net: parametrize skb_segment unit test to expand coverage
https://git.kernel.org/netdev/net-next/c/1b4fa28a8b07
- [net-next,v3,3/3] net: expand skb_segment unit test with frag_list coverage
https://git.kernel.org/netdev/net-next/c/4688ecb1385f
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:[~2023-10-11 9:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 14:41 [PATCH net-next v3 0/3] add skb_segment kunit coverage Willem de Bruijn
2023-10-09 14:41 ` [PATCH net-next v3 1/3] net: add skb_segment kunit test Willem de Bruijn
2023-10-09 14:41 ` [PATCH net-next v3 2/3] net: parametrize skb_segment unit test to expand coverage Willem de Bruijn
2023-10-09 14:41 ` [PATCH net-next v3 3/3] net: expand skb_segment unit test with frag_list coverage Willem de Bruijn
2023-10-11 9:40 ` 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=169701722775.1947.6980237139794467834.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=alexander.duyck@gmail$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=fw@strlen$(echo .)de \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=willemb@google$(echo .)com \
--cc=willemdebruijn.kernel@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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