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 3/6] cls_api: add flow_indr_block_call function
Date: Mon, 5 Aug 2019 08:02:38 +0200 [thread overview]
Message-ID: <20190805060238.GB2349@nanopsycho.orion> (raw)
In-Reply-To: <1564628627-10021-4-git-send-email-wenxu@ucloud.cn>
Re subject. You don't have "v5" in this patch. I don't understand how
that happened. Do you use --subject-prefix in git-format-patch?
next prev parent reply other threads:[~2019-08-05 6:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 3:03 [PATCH net-next v5 0/6] flow_offload: add indr-block in nf_table_offload wenxu
2019-08-01 3:03 ` [PATCH net-next v5 1/6] cls_api: modify the tc_indr_block_ing_cmd parameters wenxu
2019-08-01 3:03 ` [PATCH net-next v5 2/6] cls_api: replace block with flow_block in tc_indr_block_dev wenxu
2019-08-01 3:03 ` [PATCH net-next 3/6] cls_api: add flow_indr_block_call function wenxu
2019-08-05 6:02 ` Jiri Pirko [this message]
2019-08-05 6:26 ` wenxu
2019-08-01 3:03 ` [PATCH net-next v5 4/6] flow_offload: move tc indirect block to flow offload wenxu
2019-08-01 3:03 ` [PATCH net-next v5 5/6] flow_offload: support get flow_block immediately wenxu
2019-08-01 23:11 ` Jakub Kicinski
2019-08-02 2:47 ` wenxu
2019-08-02 2:56 ` Jakub Kicinski
2019-08-02 10:45 ` wenxu
2019-08-02 13:09 ` wenxu
2019-08-02 18:02 ` Jakub Kicinski
2019-08-02 23:19 ` wenxu
2019-08-03 0:21 ` Jakub Kicinski
2019-08-03 13:42 ` wenxu
2019-08-01 3:03 ` [PATCH net-next v5 6/6] netfilter: nf_tables_offload: support indr block call wenxu
2019-08-01 3:58 ` Yunsheng Lin
2019-08-01 4:47 ` wenxu
-- strict thread matches above, loose matches on Subject: below --
2019-07-31 8:12 [PATCH net-next 0/6] flow_offload: add indr-block in nf_table_offload wenxu
2019-07-31 8:12 ` [PATCH net-next 3/6] cls_api: add flow_indr_block_call function 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=20190805060238.GB2349@nanopsycho.orion \
--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).