netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
	xiyou.wangcong@gmail.com, dsa@cumulusnetworks.com,
	edumazet@google.com, stephen@networkplumber.org,
	daniel@iogearbox.net, alexander.h.duyck@intel.com,
	simon.horman@netronome.com, mlxsw@mellanox.com
Subject: Re: [patch net-next v4 06/10] net: sched: introduce helpers to work with filter chains
Date: Wed, 17 May 2017 14:25:28 +0200	[thread overview]
Message-ID: <20170517122528.GA9557@nanopsycho> (raw)
In-Reply-To: <ae02e4e8-3047-cd42-9c53-a2a38f8c28df@mojatatu.com>

Wed, May 17, 2017 at 02:18:00PM CEST, jhs@mojatatu.com wrote:
>On 17-05-17 05:07 AM, Jiri Pirko wrote:
>> From: Jiri Pirko <jiri@mellanox.com>
>> 
>> Introduce struct tcf_chain object and set of helpers around it. Wraps up
>> insertion, deletion and search in the filter chain.
>> 
>> Signed-off-by: Jiri Pirko <jiri@mellanox.com>
>> ---
>
>[..]
>> +
>> +static void
>> +tcf_chain_filter_chain_ptr_set(struct tcf_chain *chain,
>> +			       struct tcf_proto __rcu **p_filter_chain)
>> +
>
>What are the rules for this? Common coding style is:
>static void tcf_chain_filter_chain_ptr_set(struct tcf_chain *chain,
>                                           struct tcf_proto ..

When this would not fit 80 cols (this case), you need to wrap the
text in front of the function name. That is exacly what I did.


>
>I am sure that struct tcf_proto __rcu **p_filter_chain would
>probably hit boundary of 80 chars - but it would look cleaner
>to be consistent.
>
>Otherwise:
>Acked-by: Jamal Hadi Salim <jhs@mojatatu.com>
>
>cheers,
>jamal
>

  reply	other threads:[~2017-05-17 12:25 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-17  9:07 [patch net-next v4 00/10] net: sched: introduce multichain support for filters Jiri Pirko
2017-05-17  9:07 ` [patch net-next v4 01/10] net: sched: move tc_classify function to cls_api.c Jiri Pirko
2017-05-17 12:11   ` Jamal Hadi Salim
2017-05-17  9:07 ` [patch net-next v4 02/10] net: sched: introduce tcf block infractructure Jiri Pirko
2017-05-17 12:12   ` Jamal Hadi Salim
2017-05-17  9:07 ` [patch net-next v4 03/10] net: sched: rename tcf_destroy_chain helper Jiri Pirko
2017-05-17 12:12   ` Jamal Hadi Salim
2017-05-17  9:07 ` [patch net-next v4 04/10] net: sched: replace nprio by a bool to make the function more readable Jiri Pirko
2017-05-17 12:13   ` Jamal Hadi Salim
2017-05-17  9:07 ` [patch net-next v4 05/10] net: sched: move TC_H_MAJ macro call into tcf_auto_prio Jiri Pirko
2017-05-17 12:14   ` Jamal Hadi Salim
2017-05-17  9:07 ` [patch net-next v4 06/10] net: sched: introduce helpers to work with filter chains Jiri Pirko
2017-05-17 12:18   ` Jamal Hadi Salim
2017-05-17 12:25     ` Jiri Pirko [this message]
2017-05-17 12:39       ` Jamal Hadi Salim
2017-05-17 12:44         ` Jiri Pirko
2017-05-17 23:17           ` Joe Perches
2017-05-17  9:08 ` [patch net-next v4 07/10] net: sched: push chain dump to a separate function Jiri Pirko
2017-05-17 12:19   ` Jamal Hadi Salim
2017-05-17  9:08 ` [patch net-next v4 08/10] net: sched: introduce multichain support for filters Jiri Pirko
2017-05-17 12:27   ` Jamal Hadi Salim
2017-05-17  9:08 ` [patch net-next v4 09/10] net: sched: push tp down to action init Jiri Pirko
2017-05-17 12:30   ` Jamal Hadi Salim
2017-05-17  9:08 ` [patch net-next v4 10/10] net: sched: add termination action to allow goto chain Jiri Pirko
2017-05-17 12:31   ` Jamal Hadi Salim
2017-05-17 19:22 ` [patch net-next v4 00/10] net: sched: introduce multichain support for filters 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=20170517122528.GA9557@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=alexander.h.duyck@intel.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=dsa@cumulusnetworks.com \
    --cc=edumazet@google.com \
    --cc=jhs@mojatatu.com \
    --cc=mlxsw@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=simon.horman@netronome.com \
    --cc=stephen@networkplumber.org \
    --cc=xiyou.wangcong@gmail.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).