netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Vlad Buslov <vladbu@nvidia.com>
Cc: pabeni@redhat.com, davem@davemloft.net, kuba@kernel.org,
	shuah@kernel.org, jhs@mojatatu.com, xiyou.wangcong@gmail.com,
	jiri@resnulli.us, netdev@vger.kernel.org,
	linux-kselftest@vger.kernel.org, marcelo.leitner@gmail.com,
	shaozhengchao@huawei.com, victor@mojatatu.com
Subject: Re: [PATCH net 0/4] Fix small bugs and annoyances in tc-testing
Date: Wed, 14 Jun 2023 03:50:21 +0000	[thread overview]
Message-ID: <168671462196.18215.15524979692740732010.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230612075712.2861848-1-vladbu@nvidia.com>

Hello:

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

On Mon, 12 Jun 2023 09:57:08 +0200 you wrote:
> Vlad Buslov (4):
>   selftests/tc-testing: Fix Error: Specified qdisc kind is unknown.
>   selftests/tc-testing: Fix Error: failed to find target LOG
>   selftests/tc-testing: Fix SFB db test
>   selftests/tc-testing: Remove configs that no longer exist
> 
>  tools/testing/selftests/tc-testing/config                   | 6 +-----
>  tools/testing/selftests/tc-testing/tc-tests/qdiscs/sfb.json | 4 ++--
>  tools/testing/selftests/tc-testing/tdc.sh                   | 1 +
>  3 files changed, 4 insertions(+), 7 deletions(-)

Here is the summary with links:
  - [net,1/4] selftests/tc-testing: Fix Error: Specified qdisc kind is unknown.
    https://git.kernel.org/netdev/net/c/aef6e908b542
  - [net,2/4] selftests/tc-testing: Fix Error: failed to find target LOG
    https://git.kernel.org/netdev/net/c/b849c566ee9c
  - [net,3/4] selftests/tc-testing: Fix SFB db test
    https://git.kernel.org/netdev/net/c/b39d8c41c7a8
  - [net,4/4] selftests/tc-testing: Remove configs that no longer exist
    https://git.kernel.org/netdev/net/c/11b8b2e70a9b

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-06-14  3:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12  7:57 [PATCH net 0/4] Fix small bugs and annoyances in tc-testing Vlad Buslov
2023-06-12  7:57 ` [PATCH net 1/4] selftests/tc-testing: Fix Error: Specified qdisc kind is unknown Vlad Buslov
2023-06-12 10:35   ` shaozhengchao
2023-06-12 10:37     ` Vlad Buslov
2023-06-12 10:51       ` shaozhengchao
2023-06-12 13:22   ` Victor Nogueira
2023-06-12  7:57 ` [PATCH net 2/4] selftests/tc-testing: Fix Error: failed to find target LOG Vlad Buslov
2023-06-12  7:57 ` [PATCH net 3/4] selftests/tc-testing: Fix SFB db test Vlad Buslov
2023-06-12  7:57 ` [PATCH net 4/4] selftests/tc-testing: Remove configs that no longer exist Vlad Buslov
2023-06-12 14:06 ` [PATCH net 0/4] Fix small bugs and annoyances in tc-testing Pedro Tammela
2023-06-14  3:50 ` 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=168671462196.18215.15524979692740732010.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=marcelo.leitner@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shaozhengchao@huawei.com \
    --cc=shuah@kernel.org \
    --cc=victor@mojatatu.com \
    --cc=vladbu@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).