public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: James Simmons <jsimmons@infradead.org>
Cc: Joe Perches <joe@perches.com>,
	devel@driverdev.osuosl.org, oleg.drokin@intel.com,
	andreas.dilger@intel.com, linux-kernel@vger.kernel.org,
	Nicholas Hanley <nicholasjhanley@gmail.com>,
	lustre-devel@lists.lustre.org
Subject: Re: [PATCH] staging: lustre: o2iblnd: replace space indentation with tabs
Date: Mon, 7 Nov 2016 07:43:33 +0100	[thread overview]
Message-ID: <20161107064333.GA6336@kroah.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1611070351390.21293@casper.infradead.org>

On Mon, Nov 07, 2016 at 03:55:36AM +0000, James Simmons wrote:
> 
> > On Mon, 2016-11-07 at 02:02 +0000, James Simmons wrote:
> > > > This patch fixes all CODE_INDENT checkpatch errors in o2iblnd.
> > > Reviewed-by: James Simmons <jsimmons@infradead.org>
> > []
> > > > diff --git a/drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd.c b/drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd.c
> > []
> > > > @@ -1637,7 +1637,7 @@ int kiblnd_fmr_pool_map(struct kib_fmr_poolset *fps, struct kib_tx *tx,
> > > >  {
> > > >  	__u64 *pages = tx->tx_pages;
> > > >  	bool is_rx = (rd != tx->tx_rd);
> > > > -        bool tx_pages_mapped = 0;
> > > > +	bool tx_pages_mapped = 0;
> > 
> > It's generally better to use bool assignments to true/false not 1/0.
> 
> Nicholas can you resubmit with tx_pages_mapped = false. Looking at the 
> lustre code its the only place like this. Thanks for pointing this out.

No, make it a separate patch, don't change code when you are just
changing indentation in the same patch.

      reply	other threads:[~2016-11-07  6:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-05  0:02 [PATCH] staging: lustre: o2iblnd: replace space indentation with tabs Nicholas Hanley
2016-11-07  2:02 ` James Simmons
2016-11-07  2:47   ` Joe Perches
2016-11-07  3:55     ` James Simmons
2016-11-07  6:43       ` Greg KH [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=20161107064333.GA6336@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andreas.dilger@intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=joe@perches.com \
    --cc=jsimmons@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lustre-devel@lists.lustre.org \
    --cc=nicholasjhanley@gmail.com \
    --cc=oleg.drokin@intel.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