From: patchwork-bot+netdevbpf@kernel.org
To: renmingshuai <renmingshuai@huawei.com>
Cc: pctammela@mojatatu.com, vladbu@nvidia.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, liaichun@huawei.com, caowangbao@huawei.com,
yanan@huawei.com, liubo335@huawei.com
Subject: Re: [PATCH v2] selftests: tc-testing: add one test for flushing explicitly created chain
Date: Thu, 22 Jun 2023 00:00:21 +0000 [thread overview]
Message-ID: <168739202125.22621.9173578727280562724.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230620014939.2034054-1-renmingshuai@huawei.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 20 Jun 2023 09:49:39 +0800 you wrote:
> Add the test for additional reference to chains that are explicitly created
> by RTM_NEWCHAIN message.
> The test result:
> 1..1
> ok 1 c2b4 - soft lockup alarm will be not generated after delete the prio 0
> filter of the chain
>
> [...]
Here is the summary with links:
- [v2] selftests: tc-testing: add one test for flushing explicitly created chain
https://git.kernel.org/netdev/net-next/c/ca4fa8743537
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-06-22 0:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 1:49 renmingshuai
2023-06-20 13:48 ` Pedro Tammela
2023-06-20 14:01 ` Victor Nogueira
2023-06-22 0:00 ` 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=168739202125.22621.9173578727280562724.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=caowangbao@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=liaichun@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liubo335@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pctammela@mojatatu.com \
--cc=renmingshuai@huawei.com \
--cc=vladbu@nvidia.com \
--cc=xiyou.wangcong@gmail.com \
--cc=yanan@huawei.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
Powered by JetHome