From: Jiri Pirko <jiri@resnulli.us>
To: wenxu@ucloud.cn
Cc: pablo@netfilter.org, fw@strlen.de, jakub.kicinski@netronome.com,
netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v4 1/3] flow_offload: move tc indirect block to flow offload
Date: Mon, 29 Jul 2019 13:15:10 +0200 [thread overview]
Message-ID: <20190729111510.GF2211@nanopsycho> (raw)
In-Reply-To: <1564296769-32294-2-git-send-email-wenxu@ucloud.cn>
Sun, Jul 28, 2019 at 08:52:47AM CEST, wenxu@ucloud.cn wrote:
>From: wenxu <wenxu@ucloud.cn>
>
>move tc indirect block to flow_offload and rename
A sentence should start with capital letter.
>it to flow indirect block.The nf_tables can use the
There should be a space between "." and first letter of the next
sensence.
>indr block architecture.
>
[...]
next prev parent reply other threads:[~2019-07-29 11:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-28 6:52 [PATCH net-next v4 0/3] flow_offload: add indr-block in nf_table_offload wenxu
2019-07-28 6:52 ` [PATCH net-next v4 1/3] flow_offload: move tc indirect block to flow offload wenxu
2019-07-29 11:13 ` Jiri Pirko
2019-07-29 12:47 ` wenxu
2019-07-29 13:13 ` Jiri Pirko
2019-07-29 11:15 ` Jiri Pirko [this message]
2019-07-28 6:52 ` [PATCH net-next v4 2/3] flow_offload: Support get default block from tc immediately wenxu
2019-07-28 20:16 ` Jakub Kicinski
2019-07-29 2:43 ` wenxu
2019-07-29 4:42 ` Jakub Kicinski
2019-07-29 7:05 ` wenxu
2019-07-29 16:51 ` Jakub Kicinski
2019-07-29 7:18 ` wenxu
2019-07-29 16:55 ` Jakub Kicinski
2019-07-30 0:10 ` wenxu
2019-07-28 6:52 ` [PATCH net-next v4 3/3] netfilter: nf_tables_offload: support indr block call wenxu
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=20190729111510.GF2211@nanopsycho \
--to=jiri@resnulli.us \
--cc=fw@strlen.de \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=wenxu@ucloud.cn \
/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).