All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Joe Perches <joe@perches.com>
Cc: tcharding <me@tobin.cc>,
	Stephen Hemminger <stephen@networkplumber.org>,
	"David S. Miller" <davem@davemloft.net>,
	netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH 1/3] bridge: netfilter: checkpatch whitespace fixes
Date: Wed, 8 Jun 2016 13:52:48 +0200	[thread overview]
Message-ID: <20160608115248.GA2603@salvia> (raw)
In-Reply-To: <1465322550.25087.40.camel@perches.com>

On Tue, Jun 07, 2016 at 11:02:30AM -0700, Joe Perches wrote:
> On Tue, 2016-06-07 at 19:34 +0200, Pablo Neira Ayuso wrote:
> > On Tue, Jun 07, 2016 at 10:04:40AM -0700, Joe Perches wrote:
> > > One more question, is this chunk below correct from
> > > coding style point of view?
> > 
> >         if (info->bitmask & EBT_STP_ROOTADDR) {
> >                 verdict = 0;
> >                 for (i = 0; i < 6; i++)
> > -                       verdict |= (stpc->root[2+i] ^ c->root_addr[i]) &
> > -                                  c->root_addrmsk[i];
> > +                       verdict |= (stpc->root[2 + i] ^ c->root_addr[i]) &
> > +                               c->root_addrmsk[i];
> > 
> > I think the previous line is fine.
> 
> "2+i" or "2 + i", either is OK.
> Multiple line statement alignment doesn't
> matter much.

Sorry, I was actually refering to:

> > +                       verdict |= (stpc->root[2 + i] ^ c->root_addr[i]) &
> > +                               c->root_addrmsk[i];
                                    ^^^

instead of:

> > -                       verdict |= (stpc->root[2+i] ^ c->root_addr[i]) &
> > -                                  c->root_addrmsk[i];
                                       ^

here.

> I think either is fine and both are "don't care, don't need"
> to change from one to another to satisfy some silly whitespace
> overlord brainless script.
> 
> Perhaps it's better to add a function for this though.

I like this function idea :).

  reply	other threads:[~2016-06-08 11:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-10  1:26 [PATCH 0/3] bridge: netfilter: checkpatch fixes tcharding
2016-05-10  1:26 ` [PATCH 1/3] bridge: netfilter: checkpatch whitespace fixes tcharding
2016-06-07 15:14   ` Pablo Neira Ayuso
2016-06-07 17:04     ` Joe Perches
2016-06-07 17:34       ` Pablo Neira Ayuso
2016-06-07 18:02         ` Joe Perches
2016-06-08 11:52           ` Pablo Neira Ayuso [this message]
2016-06-08 16:52             ` Joe Perches
2016-06-08 17:31               ` Pablo Neira Ayuso
2016-06-08 17:38                 ` Pablo Neira Ayuso
2016-06-09 18:00                   ` Joe Perches
2016-06-11 10:44                     ` Tobin Harding
2016-05-10  1:26 ` [PATCH 2/3] bridge: netfilter: checkpatch data type fixes tcharding
2016-06-07 15:19   ` Pablo Neira Ayuso
2016-05-10  1:26 ` [PATCH 3/3] bridge: netfilter: checkpatch null comparison fixes tcharding
2016-06-07 15:21   ` Pablo Neira Ayuso

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=20160608115248.GA2603@salvia \
    --to=pablo@netfilter.org \
    --cc=coreteam@netfilter.org \
    --cc=davem@davemloft.net \
    --cc=joe@perches.com \
    --cc=me@tobin.cc \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=stephen@networkplumber.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 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.