public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "J . Bruce Fields" <bfields@fieldses.org>
To: Colin King <colin.king@canonical.com>
Cc: Jeff Layton <jlayton@kernel.org>,
	linux-nfs@vger.kernel.org, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nfsd: clean up indentation, increase indentation in switch statement
Date: Tue, 27 Nov 2018 17:33:57 -0500	[thread overview]
Message-ID: <20181127223357.GA15237@fieldses.org> (raw)
In-Reply-To: <20181103161253.3622-1-colin.king@canonical.com>

Thanks, applying for 4.21.--b.

On Sat, Nov 03, 2018 at 04:12:53PM +0000, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
> 
> Trivial fix to clean up indentation, add in missing tabs.
> 
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
>  fs/nfsd/nfs4state.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
> index f093fbe47133..eb129a6f9eae 100644
> --- a/fs/nfsd/nfs4state.c
> +++ b/fs/nfsd/nfs4state.c
> @@ -6230,15 +6230,15 @@ nfsd4_lockt(struct svc_rqst *rqstp, struct nfsd4_compound_state *cstate,
>  		case NFS4_READ_LT:
>  		case NFS4_READW_LT:
>  			file_lock->fl_type = F_RDLCK;
> -		break;
> +			break;
>  		case NFS4_WRITE_LT:
>  		case NFS4_WRITEW_LT:
>  			file_lock->fl_type = F_WRLCK;
> -		break;
> +			break;
>  		default:
>  			dprintk("NFSD: nfs4_lockt: bad lock type!\n");
>  			status = nfserr_inval;
> -		goto out;
> +			goto out;
>  	}
>  
>  	lo = find_lockowner_str(cstate->clp, &lockt->lt_owner);
> -- 
> 2.19.1

      reply	other threads:[~2018-11-27 22:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-03 16:12 [PATCH] nfsd: clean up indentation, increase indentation in switch statement Colin King
2018-11-27 22:33 ` 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=20181127223357.GA15237@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=colin.king@canonical.com \
    --cc=jlayton@kernel.org \
    --cc=kernel-janitors@vger.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