From: David Miller <davem@davemloft.net>
To: fw@strlen.de
Cc: pablo@netfilter.org, netdev@vger.kernel.org,
f.fainelli@gmail.com, jiri@mellanox.com, mkubecek@suse.cz
Subject: Re: [net-next,v5,00/12] add flow_rule infrastructure
Date: Tue, 11 Dec 2018 11:14:20 -0800 (PST) [thread overview]
Message-ID: <20181211.111420.9962444018507543.davem@davemloft.net> (raw)
In-Reply-To: <20181211153519.GA920@strlen.de>
From: Florian Westphal <fw@strlen.de>
Date: Tue, 11 Dec 2018 16:35:19 +0100
> Pablo Neira Ayuso <pablo@netfilter.org> wrote:
>
> [ trimming CCs ]
>
>> This is another iteration of the in-kernel intermediate representation
>> (IR) that allows to express ACL hardware offloads using one unified
>> representation from the driver side for the ethtool and the tc
>> frontends [1] [2] [3].
>
> [..]
>
> This is marked 'rejected' in patchwork, what happened?
Pablo is not being honest about his true intentions and long term
goals with this series. Or also brought up fundamental objections
against previous versions of this series which were not sufficiently
addressed by Pablo.
My personal concern has been brought up several times.
I am not going to restate the same thing over and over, and he hasn't
fixed up his introductory posting in response to my concerns in any
meaningful and full way.
Therefore, if I feel like my and Or's feedback will keep being
ignored, I will keep rejecting these changes.
next prev parent reply other threads:[~2018-12-11 19:14 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 22:39 [PATCH net-next,v5 00/12] add flow_rule infrastructure Pablo Neira Ayuso
2018-12-06 22:39 ` [PATCH net-next,v5 01/12] flow_offload: add flow_rule and flow_match structures and use them Pablo Neira Ayuso
2018-12-08 8:27 ` Jiri Pirko
2018-12-06 22:39 ` [PATCH net-next,v5 02/12] net/mlx5e: support for two independent packet edit actions Pablo Neira Ayuso
2018-12-08 8:49 ` Jiri Pirko
2018-12-06 22:39 ` [PATCH net-next,v5 03/12] flow_offload: add flow action infrastructure Pablo Neira Ayuso
2018-12-08 8:49 ` Jiri Pirko
2018-12-06 22:39 ` [PATCH net-next,v5 04/12] cls_api: add translator to flow_action representation Pablo Neira Ayuso
2018-12-08 8:49 ` Jiri Pirko
2018-12-06 22:39 ` [PATCH net-next,v5 05/12] flow_offload: add statistics retrieval infrastructure and use it Pablo Neira Ayuso
2018-12-08 12:56 ` Jiri Pirko
2018-12-06 22:39 ` [PATCH net-next,v5 06/12] drivers: net: use flow action infrastructure Pablo Neira Ayuso
2018-12-08 12:59 ` Jiri Pirko
2018-12-06 22:39 ` [PATCH net-next,v5 07/12] cls_flower: don't expose TC actions to drivers anymore Pablo Neira Ayuso
2018-12-08 12:57 ` Jiri Pirko
2018-12-06 22:39 ` [PATCH net-next,v5 08/12] flow_offload: add wake-up-on-lan and queue to flow_action Pablo Neira Ayuso
2018-12-08 13:12 ` Jiri Pirko
2018-12-06 22:39 ` [PATCH net-next,v5 09/12] ethtool: add ethtool_rx_flow_spec to flow_rule structure translator Pablo Neira Ayuso
2018-12-08 13:14 ` Jiri Pirko
2018-12-06 22:40 ` [PATCH net-next,v5 10/12] dsa: bcm_sf2: use flow_rule infrastructure Pablo Neira Ayuso
2018-12-08 17:22 ` Jiri Pirko
2018-12-06 22:40 ` [PATCH net-next,v5 11/12] qede: place ethtool_rx_flow_spec after code after TC flower codebase Pablo Neira Ayuso
2018-12-08 17:22 ` Jiri Pirko
2018-12-06 22:40 ` [PATCH net-next,v5 12/12] qede: use ethtool_rx_flow_rule() to remove duplicated parser code Pablo Neira Ayuso
2018-12-11 15:35 ` [net-next,v5,00/12] add flow_rule infrastructure Florian Westphal
2018-12-11 19:14 ` David Miller [this message]
2018-12-11 20:59 ` Or Gerlitz
2018-12-11 22:17 ` Jakub Kicinski
2018-12-13 10:06 ` Or Gerlitz
2018-12-13 19:23 ` Jakub Kicinski
2018-12-13 19:54 ` Pablo Neira Ayuso
2018-12-13 20:17 ` Michal Kubecek
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=20181211.111420.9962444018507543.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=fw@strlen.de \
--cc=jiri@mellanox.com \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
/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).