All of lore.kernel.org
 help / color / mirror / Atom feed
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,
	willemdebruijn.kernel@gmail.com, petrm@nvidia.com,
	gal@nvidia.com
Subject: Re: [PATCH net-next v4 0/4] selftests: drv-net: add a simple TSO test
Date: Thu, 20 Feb 2025 03:30:31 +0000	[thread overview]
Message-ID: <174002223100.830506.13522479369749861704.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250218225426.77726-1-kuba@kernel.org>

Hello:

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

On Tue, 18 Feb 2025 14:54:22 -0800 you wrote:
> Add a simple test for exercising TSO over tunnels.
> 
> Similarly to csum test we want to iterate over ip versions.
> Rework how addresses are stored in env to make this easier.
> 
> v4:
>  - [patch 3] fix f-strings on Python < 3.12
>  - [patch 4] fix v4/v6 test naming
>  - [patch 4] correctly select the inner vs outer protocol version
>  - [patch 4] enable mangleid if tunnel is supported via GSO partial
> v3: https://lore.kernel.org/20250217194200.3011136-1-kuba@kernel.org
>  - [patch 3] new patch
>  - [patch 4] rework after new patch added
> v2: https://lore.kernel.org/20250214234631.2308900-1-kuba@kernel.org
>  - [patch 1] check for IP being on multiple ifcs
>  - [patch 4] lower max noise
>  - [patch 4] mention header overhead in the comment
>  - [patch 4] fix the basic v4 TSO feature name
>  - [patch 4] also run a stream with just GSO partial for tunnels
> v1: https://lore.kernel.org/20250213003454.1333711-1-kuba@kernel.org
> 
> [...]

Here is the summary with links:
  - [net-next,v4,1/4] selftests: drv-net: resolve remote interface name
    https://git.kernel.org/netdev/net-next/c/2217bcb49149
  - [net-next,v4,2/4] selftests: drv-net: get detailed interface info
    https://git.kernel.org/netdev/net-next/c/2aefca8e1fa8
  - [net-next,v4,3/4] selftests: drv-net: store addresses in dict indexed by ipver
    https://git.kernel.org/netdev/net-next/c/de94e8697405
  - [net-next,v4,4/4] selftests: drv-net: add a simple TSO test
    https://git.kernel.org/netdev/net-next/c/0d0f4174f6c8

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



      parent reply	other threads:[~2025-02-20  3:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18 22:54 [PATCH net-next v4 0/4] selftests: drv-net: add a simple TSO test Jakub Kicinski
2025-02-18 22:54 ` [PATCH net-next v4 1/4] selftests: drv-net: resolve remote interface name Jakub Kicinski
2025-02-18 22:54 ` [PATCH net-next v4 2/4] selftests: drv-net: get detailed interface info Jakub Kicinski
2025-02-18 22:54 ` [PATCH net-next v4 3/4] selftests: drv-net: store addresses in dict indexed by ipver Jakub Kicinski
2025-02-19  2:24   ` Willem de Bruijn
2025-02-18 22:54 ` [PATCH net-next v4 4/4] selftests: drv-net: add a simple TSO test Jakub Kicinski
2025-02-19  2:24   ` Willem de Bruijn
2025-02-20  3: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=174002223100.830506.13522479369749861704.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=gal@nvidia.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=petrm@nvidia.com \
    --cc=willemdebruijn.kernel@gmail.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.