All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] net: ipv6: netfilter: Format block comments.
@ 2017-03-29  8:39 Arushi Singhal
  2017-04-07 16:15 ` [Outreachy kernel] " Pablo Neira Ayuso
  0 siblings, 1 reply; 3+ messages in thread
From: Arushi Singhal @ 2017-03-29  8:39 UTC (permalink / raw)
  To: pablo
  Cc: Jozsef Kadlecsik, David S. Miller, Alexey Kuznetsov, James Morris,
	Hideaki YOSHIFUJI, Patrick McHardy, netfilter-devel, coreteam,
	netdev, linux-kernel, outreachy-kernel

Fix checkpatch warnings:
WARNING: Block comments use a trailing */ on a separate line
WARNING: Block comments use * on subsequent lines

Signed-off-by: Arushi Singhal <arushisinghal19971997@gmail.com>
---
 net/ipv6/netfilter/ip6_tables.c | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/net/ipv6/netfilter/ip6_tables.c b/net/ipv6/netfilter/ip6_tables.c
index b8cb61c27aa1..ac69ce3bfa1e 100644
--- a/net/ipv6/netfilter/ip6_tables.c
+++ b/net/ipv6/netfilter/ip6_tables.c
@@ -51,14 +51,14 @@ void *ip6t_alloc_initial_table(const struct xt_table *info)
 }
 EXPORT_SYMBOL_GPL(ip6t_alloc_initial_table);
 
-/*
-   We keep a set of rules for each CPU, so we can avoid write-locking
-   them in the softirq when updating the counters and therefore
-   only need to read-lock in the softirq; doing a write_lock_bh() in user
-   context stops packets coming through and allows user context to read
-   the counters or update the rules.
-
-   Hence the start of any table is given by get_table() below.  */
+/* We keep a set of rules for each CPU, so we can avoid write-locking
+ * them in the softirq when updating the counters and therefore
+ * only need to read-lock in the softirq; doing a write_lock_bh() in user
+ * context stops packets coming through and allows user context to read
+ * the counters or update the rules.
+ *
+ * Hence the start of any table is given by get_table() below.
+ */
 
 /* Returns whether matches rule or not. */
 /* Performance critical - called for every packet */
-- 
2.11.0

^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [Outreachy kernel] [PATCH] net: ipv6: netfilter: Format block comments.
  2017-03-29  8:39 [PATCH] net: ipv6: netfilter: Format block comments Arushi Singhal
@ 2017-04-07 16:15 ` Pablo Neira Ayuso
  2017-04-08 15:13   ` Arushi Singhal
  0 siblings, 1 reply; 3+ messages in thread
From: Pablo Neira Ayuso @ 2017-04-07 16:15 UTC (permalink / raw)
  To: Arushi Singhal
  Cc: Jozsef Kadlecsik, David S. Miller, Alexey Kuznetsov, James Morris,
	Hideaki YOSHIFUJI, Patrick McHardy, netfilter-devel, coreteam,
	netdev, linux-kernel, outreachy-kernel

On Wed, Mar 29, 2017 at 02:09:43PM +0530, Arushi Singhal wrote:
> Fix checkpatch warnings:
> WARNING: Block comments use a trailing */ on a separate line
> WARNING: Block comments use * on subsequent lines
> 
> Signed-off-by: Arushi Singhal <arushisinghal19971997@gmail.com>
> ---
>  net/ipv6/netfilter/ip6_tables.c | 16 ++++++++--------
>  1 file changed, 8 insertions(+), 8 deletions(-)
> 
> diff --git a/net/ipv6/netfilter/ip6_tables.c b/net/ipv6/netfilter/ip6_tables.c
> index b8cb61c27aa1..ac69ce3bfa1e 100644
> --- a/net/ipv6/netfilter/ip6_tables.c
> +++ b/net/ipv6/netfilter/ip6_tables.c
> @@ -51,14 +51,14 @@ void *ip6t_alloc_initial_table(const struct xt_table *info)
>  }
>  EXPORT_SYMBOL_GPL(ip6t_alloc_initial_table);
>  
> -/*
> -   We keep a set of rules for each CPU, so we can avoid write-locking
> -   them in the softirq when updating the counters and therefore
> -   only need to read-lock in the softirq; doing a write_lock_bh() in user
> -   context stops packets coming through and allows user context to read
> -   the counters or update the rules.
> -
> -   Hence the start of any table is given by get_table() below.  */
> +/* We keep a set of rules for each CPU, so we can avoid write-locking
> + * them in the softirq when updating the counters and therefore
> + * only need to read-lock in the softirq; doing a write_lock_bh() in user
> + * context stops packets coming through and allows user context to read
> + * the counters or update the rules.
> + *
> + * Hence the start of any table is given by get_table() below.
> + */

This comment is obsolete and should go.

We have no set of rules per CPU anymore.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Outreachy kernel] [PATCH] net: ipv6: netfilter: Format block comments.
  2017-04-07 16:15 ` [Outreachy kernel] " Pablo Neira Ayuso
@ 2017-04-08 15:13   ` Arushi Singhal
  0 siblings, 0 replies; 3+ messages in thread
From: Arushi Singhal @ 2017-04-08 15:13 UTC (permalink / raw)
  To: Pablo Neira Ayuso
  Cc: Jozsef Kadlecsik, David S. Miller, Alexey Kuznetsov, James Morris,
	Hideaki YOSHIFUJI, Patrick McHardy, netfilter-devel, coreteam,
	netdev, LKML, outreachy-kernel

[-- Attachment #1: Type: text/plain, Size: 1874 bytes --]

On Fri, Apr 7, 2017 at 9:45 PM, Pablo Neira Ayuso <pablo@netfilter.org>
wrote:

> On Wed, Mar 29, 2017 at 02:09:43PM +0530, Arushi Singhal wrote:
> > Fix checkpatch warnings:
> > WARNING: Block comments use a trailing */ on a separate line
> > WARNING: Block comments use * on subsequent lines
> >
> > Signed-off-by: Arushi Singhal <arushisinghal19971997@gmail.com>
> > ---
> >  net/ipv6/netfilter/ip6_tables.c | 16 ++++++++--------
> >  1 file changed, 8 insertions(+), 8 deletions(-)
> >
> > diff --git a/net/ipv6/netfilter/ip6_tables.c b/net/ipv6/netfilter/ip6_
> tables.c
> > index b8cb61c27aa1..ac69ce3bfa1e 100644
> > --- a/net/ipv6/netfilter/ip6_tables.c
> > +++ b/net/ipv6/netfilter/ip6_tables.c
> > @@ -51,14 +51,14 @@ void *ip6t_alloc_initial_table(const struct
> xt_table *info)
> >  }
> >  EXPORT_SYMBOL_GPL(ip6t_alloc_initial_table);
> >
> > -/*
> > -   We keep a set of rules for each CPU, so we can avoid write-locking
> > -   them in the softirq when updating the counters and therefore
> > -   only need to read-lock in the softirq; doing a write_lock_bh() in
> user
> > -   context stops packets coming through and allows user context to read
> > -   the counters or update the rules.
> > -
> > -   Hence the start of any table is given by get_table() below.  */
> > +/* We keep a set of rules for each CPU, so we can avoid write-locking
> > + * them in the softirq when updating the counters and therefore
> > + * only need to read-lock in the softirq; doing a write_lock_bh() in
> user
> > + * context stops packets coming through and allows user context to read
> > + * the counters or update the rules.
> > + *
> > + * Hence the start of any table is given by get_table() below.
> > + */
>
> This comment is obsolete and should go.
>
> We have no set of rules per CPU anymore.
>
Hi Pablo
So should I fix this by removing these comments.

Thanks
Arushi

[-- Attachment #2: Type: text/html, Size: 2600 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2017-04-08 15:13 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-03-29  8:39 [PATCH] net: ipv6: netfilter: Format block comments Arushi Singhal
2017-04-07 16:15 ` [Outreachy kernel] " Pablo Neira Ayuso
2017-04-08 15:13   ` Arushi Singhal

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.