From: patchwork-bot+netdevbpf@kernel.org
To: Baowen Zheng <baowen.zheng@corigine.com>
Cc: dsahern@gmail.com, netdev@vger.kernel.org,
oss-drivers@corigine.com, jhs@mojatatu.com, victor@mojatatu.com,
simon.horman@corigine.com
Subject: Re: [PATCH iproute2-next v2] tc: add skip_hw and skip_sw to control action offload
Date: Tue, 01 Feb 2022 03:50:10 +0000 [thread overview]
Message-ID: <164368741051.29164.7274079279797936323.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1643180079-17097-1-git-send-email-baowen.zheng@corigine.com>
Hello:
This patch was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Wed, 26 Jan 2022 14:54:39 +0800 you wrote:
> Add skip_hw and skip_sw flags for user to control whether
> offload action to hardware.
>
> Also we add hw_count to show how many hardwares accept to offload
> the action.
>
> Change man page to describe the usage of skip_sw and skip_hw flag.
>
> [...]
Here is the summary with links:
- [iproute2-next,v2] tc: add skip_hw and skip_sw to control action offload
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=f4cd4f127047
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:[~2022-02-01 3:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 6:54 [PATCH iproute2-next v2] tc: add skip_hw and skip_sw to control action offload Baowen Zheng
2022-01-26 13:41 ` Victor Nogueira
2022-01-31 19:40 ` Jamal Hadi Salim
2022-02-02 8:39 ` Roi Dayan
2022-02-02 8:46 ` Roi Dayan
2022-02-02 9:37 ` Baowen Zheng
2022-02-02 11:15 ` Roi Dayan
2022-02-02 11:47 ` Jamal Hadi Salim
2022-02-11 10:01 ` Baowen Zheng
2022-02-16 12:51 ` Jamal Hadi Salim
2022-02-16 14:18 ` Roi Dayan
2022-02-17 1:51 ` Baowen Zheng
2022-02-01 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=164368741051.29164.7274079279797936323.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=baowen.zheng@corigine.com \
--cc=dsahern@gmail.com \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=simon.horman@corigine.com \
--cc=victor@mojatatu.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).