Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
Cc: Jeff Layton <jlayton@kernel.org>,
	linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nfsd: use true and false for boolean values
Date: Thu, 2 Aug 2018 09:34:45 -0400	[thread overview]
Message-ID: <20180802133445.GB30706@fieldses.org> (raw)
In-Reply-To: <20180802004405.GA23995@embeddedor.com>

OK, applied for for-4.19, thanks.--b.

On Wed, Aug 01, 2018 at 07:44:05PM -0500, Gustavo A. R. Silva wrote:
> Return statements in functions returning bool should use true or false
> instead of an integer value.
> 
> This issue was detected with the help of Coccinelle.
> 
> Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com>
> ---
>  fs/nfsd/nfsfh.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/fs/nfsd/nfsfh.c b/fs/nfsd/nfsfh.c
> index a008e76..b319080 100644
> --- a/fs/nfsd/nfsfh.c
> +++ b/fs/nfsd/nfsfh.c
> @@ -451,7 +451,7 @@ static bool fsid_type_ok_for_exp(u8 fsid_type, struct svc_export *exp)
>  	switch (fsid_type) {
>  	case FSID_DEV:
>  		if (!old_valid_dev(exp_sb(exp)->s_dev))
> -			return 0;
> +			return false;
>  		/* FALL THROUGH */
>  	case FSID_MAJOR_MINOR:
>  	case FSID_ENCODE_DEV:
> @@ -461,13 +461,13 @@ static bool fsid_type_ok_for_exp(u8 fsid_type, struct svc_export *exp)
>  	case FSID_UUID8:
>  	case FSID_UUID16:
>  		if (!is_root_export(exp))
> -			return 0;
> +			return false;
>  		/* fall through */
>  	case FSID_UUID4_INUM:
>  	case FSID_UUID16_INUM:
>  		return exp->ex_uuid != NULL;
>  	}
> -	return 1;
> +	return true;
>  }
>  
>  
> -- 
> 2.7.4

      reply	other threads:[~2018-08-02 15:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-02  0:44 [PATCH] nfsd: use true and false for boolean values Gustavo A. R. Silva
2018-08-02 13:34 ` J. Bruce Fields [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=20180802133445.GB30706@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=gustavo@embeddedor.com \
    --cc=jlayton@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.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