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, shuah@kernel.org,
pabeni@redhat.com, kuba@kernel.org, victor@mojatatu.com,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
lkft@linaro.org, naresh.kamboju@linaro.org
Subject: Re: [PATCH net-next] selftests/tc-testing: require an up to date iproute2 for blockcast tests
Date: Tue, 05 Mar 2024 03:40:26 +0000 [thread overview]
Message-ID: <170961002605.3516.18175318406387875689.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240229143825.1373550-1-pctammela@mojatatu.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 29 Feb 2024 11:38:25 -0300 you wrote:
> Add the dependsOn test check for all the mirred blockcast tests.
> It will prevent the issue reported by LKFT which happens when an older
> iproute2 is used to run the current tdc.
>
> Tests are skipped if the dependsOn check fails.
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> Signed-off-by: Pedro Tammela <pctammela@mojatatu.com>
>
> [...]
Here is the summary with links:
- [net-next] selftests/tc-testing: require an up to date iproute2 for blockcast tests
https://git.kernel.org/netdev/net-next/c/dcfaf1f758ee
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:[~2024-03-05 3:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 14:38 [PATCH net-next] selftests/tc-testing: require an up to date iproute2 for blockcast tests Pedro Tammela
2024-03-01 12:24 ` Naresh Kamboju
2024-03-01 12:32 ` Pedro Tammela
2024-03-05 3: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=170961002605.3516.18175318406387875689.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkft@linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pctammela@mojatatu.com \
--cc=shuah@kernel.org \
--cc=victor@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox