From: patchwork-bot+netdevbpf@kernel.org
To: Vlad Buslov <vladbu@nvidia.com>
Cc: memxor@gmail.com, xiyou.wangcong@gmail.com, davem@davemloft.net,
jhs@mojatatu.com, jiri@resnulli.us, kuba@kernel.org,
toke@redhat.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next] tc-testing: add simple action change test
Date: Wed, 31 Mar 2021 00:20:10 +0000 [thread overview]
Message-ID: <161715001058.3850.13772855808502684032.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210330104110.25360-1-vladbu@nvidia.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Tue, 30 Mar 2021 13:41:10 +0300 you wrote:
> Use act_simple to verify that action created with 'tc actions change'
> command exists after command returns. The goal is to verify internal action
> API reference counting to ensure that the case when netlink message has
> NLM_F_REPLACE flag set but action with specified index doesn't exist is
> handled correctly.
>
> Signed-off-by: Vlad Buslov <vladbu@nvidia.com>
>
> [...]
Here is the summary with links:
- [net-next] tc-testing: add simple action change test
https://git.kernel.org/netdev/net-next/c/e48792a9ec78
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-03-31 0:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 22:53 [PATCH v2 1/1] net: sched: bump refcount for new action in ACT replace mode Kumar Kartikeya Dwivedi
2021-03-30 10:32 ` Vlad Buslov
2021-03-30 10:41 ` [PATCH net-next] tc-testing: add simple action change test Vlad Buslov
2021-03-31 0:20 ` patchwork-bot+netdevbpf [this message]
2021-03-31 4:40 ` [PATCH v2 1/1] net: sched: bump refcount for new action in ACT replace mode Cong Wang
2021-03-31 7:59 ` Vlad Buslov
2021-03-31 8:37 ` [PATCH net-next v3] " Kumar Kartikeya Dwivedi
2021-03-31 14:08 ` Vlad Buslov
2021-03-31 8:38 ` [PATCH v2 1/1] " Kumar Kartikeya Dwivedi
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=161715001058.3850.13772855808502684032.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-kernel@vger.kernel.org \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=toke@redhat.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 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.