From: Jiri Pirko <jiri@resnulli.us>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
ecree@solarflare.com, mlxsw@mellanox.com
Subject: Re: [patch net-next] flow_offload: use flow_action_for_each in flow_action_mixed_hw_stats_types_check()
Date: Tue, 10 Mar 2020 11:03:52 +0100 [thread overview]
Message-ID: <20200310100352.GA2211@nanopsycho> (raw)
In-Reply-To: <20200309183325.yw2c4swbwv7xqlm2@salvia>
Mon, Mar 09, 2020 at 07:33:25PM CET, pablo@netfilter.org wrote:
>On Mon, Mar 09, 2020 at 06:44:47PM +0100, Jiri Pirko wrote:
>> Instead of manually iterating over entries, use flow_action_for_each
>> helper. Move the helper and wrap it to fit to 80 cols on the way.
>>
>> Signed-off-by: Jiri Pirko <jiri@resnulli.us>
>> ---
>> include/net/flow_offload.h | 10 ++++++----
>> 1 file changed, 6 insertions(+), 4 deletions(-)
>>
>> diff --git a/include/net/flow_offload.h b/include/net/flow_offload.h
>> index 64807aa03cee..7b7bd9215156 100644
>> --- a/include/net/flow_offload.h
>> +++ b/include/net/flow_offload.h
>> @@ -256,6 +256,11 @@ static inline bool flow_offload_has_one_action(const struct flow_action *action)
>> return action->num_entries == 1;
>> }
>>
>> +#define flow_action_for_each(__i, __act, __actions) \
>> + for (__i = 0, __act = &(__actions)->entries[0]; \
>> + __i < (__actions)->num_entries; \
>> + __act = &(__actions)->entries[++__i])
>> +
>> static inline bool
>> flow_action_mixed_hw_stats_types_check(const struct flow_action *action,
>> struct netlink_ext_ack *extack)
>> @@ -267,7 +272,7 @@ flow_action_mixed_hw_stats_types_check(const struct flow_action *action,
>> if (flow_offload_has_one_action(action))
>> return true;
>>
>> - for (i = 0; i < action->num_entries; i++) {
>> + flow_action_for_each(i, action_entry, action) {
>> action_entry = &action->entries[i];
> ^^^
>
>action_entry is set twice, right? One from flow_action_for_each() and
>again here. You can probably remove this line too.
Correct. Will send v2
prev parent reply other threads:[~2020-03-10 10:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 17:44 [patch net-next] flow_offload: use flow_action_for_each in flow_action_mixed_hw_stats_types_check() Jiri Pirko
2020-03-09 18:07 ` Edward Cree
2020-03-09 18:33 ` Pablo Neira Ayuso
2020-03-10 10:03 ` Jiri Pirko [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=20200310100352.GA2211@nanopsycho \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=ecree@solarflare.com \
--cc=kuba@kernel.org \
--cc=mlxsw@mellanox.com \
--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).