All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Pedro Tammela <pctammela@mojatatu.com>
Cc: netdev@vger.kernel.org, jhs@mojatatu.com,
	xiyou.wangcong@gmail.com, jiri@resnulli.us, davem@davemloft.net,
	kuba@kernel.org, pabeni@redhat.com, edumazet@google.com,
	linux-kselftest@vger.kernel.org, bpf@vger.kernel.org,
	llvm@lists.linux.dev
Subject: Re: [PATCH net-next 0/5] selftests: tc-testing: updates and cleanups for tdc
Date: Tue, 28 Nov 2023 02:20:28 +0000	[thread overview]
Message-ID: <170113802890.29254.11697314055682451731.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231124154248.315470-1-pctammela@mojatatu.com>

Hello:

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

On Fri, 24 Nov 2023 12:42:43 -0300 you wrote:
> Address the recommendations from the previous series and cleanup some
> leftovers.
> 
> Pedro Tammela (5):
>   selftests: tc-testing: remove buildebpf plugin
>   selftests: tc-testing: remove unnecessary time.sleep
>   selftests: tc-testing: prefix iproute2 functions with "ipr2"
>   selftests: tc-testing: cleanup on Ctrl-C
>   selftests: tc-testing: remove unused import
> 
> [...]

Here is the summary with links:
  - [net-next,1/5] selftests: tc-testing: remove buildebpf plugin
    https://git.kernel.org/netdev/net-next/c/a79d8ba734bd
  - [net-next,2/5] selftests: tc-testing: remove unnecessary time.sleep
    https://git.kernel.org/netdev/net-next/c/8059e68b9928
  - [net-next,3/5] selftests: tc-testing: prefix iproute2 functions with "ipr2"
    https://git.kernel.org/netdev/net-next/c/56e16bc69bb7
  - [net-next,4/5] selftests: tc-testing: cleanup on Ctrl-C
    https://git.kernel.org/netdev/net-next/c/501679f5d4a4
  - [net-next,5/5] selftests: tc-testing: remove unused import
    https://git.kernel.org/netdev/net-next/c/ed346fccfc40

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



      parent reply	other threads:[~2023-11-28  2:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-24 15:42 [PATCH net-next 0/5] selftests: tc-testing: updates and cleanups for tdc Pedro Tammela
2023-11-24 15:42 ` [PATCH net-next 1/5] selftests: tc-testing: remove buildebpf plugin Pedro Tammela
2023-11-28  2:15   ` Jakub Kicinski
2023-11-24 15:42 ` [PATCH net-next 2/5] selftests: tc-testing: remove unnecessary time.sleep Pedro Tammela
2023-11-24 15:42 ` [PATCH net-next 3/5] selftests: tc-testing: prefix iproute2 functions with "ipr2" Pedro Tammela
2023-11-24 15:42 ` [PATCH net-next 4/5] selftests: tc-testing: cleanup on Ctrl-C Pedro Tammela
2023-11-24 15:42 ` [PATCH net-next 5/5] selftests: tc-testing: remove unused import Pedro Tammela
2023-11-27 15:48 ` [PATCH net-next 0/5] selftests: tc-testing: updates and cleanups for tdc Jamal Hadi Salim
2023-11-28  2:20 ` 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=170113802890.29254.11697314055682451731.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pctammela@mojatatu.com \
    --cc=xiyou.wangcong@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.