From: Jiri Pirko <jiri@resnulli.us>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, saeedm@mellanox.com,
pablo@netfilter.org, ecree@solarflare.com
Subject: [patch net-next 0/3] flow_offload: follow-ups to HW stats type patchset
Date: Tue, 10 Mar 2020 16:49:06 +0100 [thread overview]
Message-ID: <20200310154909.3970-1-jiri@resnulli.us> (raw)
This patchset includes couple of patches in reaction to the discussions
to the original HW stats patchset. The first patch is a fix,
the other two patches are basically cosmetics.
Jiri Pirko (3):
flow_offload: fix allowed types check
flow_offload: turn hw_stats_type into dedicated enum
flow_offload: restrict driver to pass one allowed bit to
flow_action_hw_stats_types_check()
.../net/ethernet/mellanox/mlx5/core/en_tc.c | 4 +-
include/net/flow_offload.h | 46 +++++++++++++------
2 files changed, 35 insertions(+), 15 deletions(-)
--
2.21.1
next reply other threads:[~2020-03-10 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 15:49 Jiri Pirko [this message]
2020-03-10 15:49 ` [patch net-next 1/3] flow_offload: fix allowed types check Jiri Pirko
2020-03-10 15:49 ` [patch net-next 2/3] flow_offload: turn hw_stats_type into dedicated enum Jiri Pirko
2020-03-10 15:49 ` [patch net-next 3/3] flow_offload: restrict driver to pass one allowed bit to flow_action_hw_stats_types_check() Jiri Pirko
2020-03-10 17:47 ` [patch net-next 0/3] flow_offload: follow-ups to HW stats type patchset Edward Cree
2020-03-10 19:05 ` Jakub Kicinski
2020-03-11 7:19 ` Jiri Pirko
2020-03-11 20:30 ` Jakub Kicinski
2020-03-12 7:03 ` Jiri Pirko
2020-03-12 19:40 ` Jakub Kicinski
2020-03-10 23:04 ` David Miller
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=20200310154909.3970-1-jiri@resnulli.us \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=ecree@solarflare.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=saeedm@mellanox.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).