linux-cifs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve French <smfrench@gmail.com>
To: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Cc: Steve French <sfrench@samba.org>,
	CIFS <linux-cifs@vger.kernel.org>,
	samba-technical <samba-technical@lists.samba.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cifs: Fix inconsistent indenting
Date: Wed, 19 May 2021 21:12:11 -0500	[thread overview]
Message-ID: <CAH2r5mvPTFcueM4VotLvQfiNLDeG0_CMXKQdUtyMYstXYznJqQ@mail.gmail.com> (raw)
In-Reply-To: <1621421227-34130-1-git-send-email-jiapeng.chong@linux.alibaba.com>

merged into cifs-2.6.git for-next

On Wed, May 19, 2021 at 2:27 PM Jiapeng Chong
<jiapeng.chong@linux.alibaba.com> wrote:
>
> Eliminate the follow smatch warning:
>
> fs/cifs/fs_context.c:1148 smb3_fs_context_parse_param() warn:
> inconsistent indenting.
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
> ---
>  fs/cifs/fs_context.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/cifs/fs_context.c b/fs/cifs/fs_context.c
> index 5d21cd9..92d4ab0 100644
> --- a/fs/cifs/fs_context.c
> +++ b/fs/cifs/fs_context.c
> @@ -1145,7 +1145,7 @@ static int smb3_fs_context_parse_param(struct fs_context *fc,
>                 /* if iocharset not set then load_nls_default
>                  * is used by caller
>                  */
> -                cifs_dbg(FYI, "iocharset set to %s\n", ctx->iocharset);
> +               cifs_dbg(FYI, "iocharset set to %s\n", ctx->iocharset);
>                 break;
>         case Opt_netbiosname:
>                 memset(ctx->source_rfc1001_name, 0x20,
> --
> 1.8.3.1
>


-- 
Thanks,

Steve

      reply	other threads:[~2021-05-20  2:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19 10:47 [PATCH] cifs: Fix inconsistent indenting Jiapeng Chong
2021-05-20  2:12 ` Steve French [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=CAH2r5mvPTFcueM4VotLvQfiNLDeG0_CMXKQdUtyMYstXYznJqQ@mail.gmail.com \
    --to=smfrench@gmail.com \
    --cc=jiapeng.chong@linux.alibaba.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=samba-technical@lists.samba.org \
    --cc=sfrench@samba.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;
as well as URLs for NNTP newsgroup(s).