linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: huzhi001@208suo.com
Cc: dsterba@suse.com, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] VFS: Fix seven errors in bitmap.c
Date: Fri, 14 Jul 2023 12:46:55 +0200	[thread overview]
Message-ID: <20230714104655.GH20457@suse.cz> (raw)
In-Reply-To: <80ff0222e0fc0b8e25ae4837b76bce2d@208suo.com>

On Fri, Jul 14, 2023 at 03:14:18PM +0800, huzhi001@208suo.com wrote:
> The following checkpatch errors are removed:
> ERROR: space required after that ',' (ctx:VxV)
> ERROR: space required after that ',' (ctx:VxV)
> ERROR: space required after that ',' (ctx:VxV)
> ERROR: space required after that ',' (ctx:VxV)
> ERROR: space required after that ',' (ctx:VxV)
> ERROR: space required after that ',' (ctx:VxV)
> ERROR: space required after that ',' (ctx:VxV)

The AFFS module gets only bug fixes (as can be seen in the MAINTAINERS
file) or API updates, not coding style fixes.

The sources have way more stylistic things that checkpatch does not like
but we are not going to fix them:

total: 0 errors, 1 warnings, 189 lines checked
total: 1 errors, 5 warnings, 543 lines checked
total: 7 errors, 4 warnings, 365 lines checked
total: 1 errors, 1 warnings, 144 lines checked
total: 2 errors, 13 warnings, 1009 lines checked
total: 8 errors, 12 warnings, 422 lines checked
total: 0 errors, 2 warnings, 584 lines checked
total: 15 errors, 13 warnings, 681 lines checked
total: 1 errors, 2 warnings, 77 lines checked
total: 4 errors, 10 warnings, 328 lines checked
total: 4 errors, 0 warnings, 148 lines checked

      reply	other threads:[~2023-07-14 10:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tencent_CE461BFFDACFEA943A778650FB672D9E3207@qq.com>
2023-07-14  7:14 ` [PATCH] VFS: Fix seven errors in bitmap.c huzhi001
2023-07-14 10:46   ` David Sterba [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=20230714104655.GH20457@suse.cz \
    --to=dsterba@suse.cz \
    --cc=dsterba@suse.com \
    --cc=huzhi001@208suo.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).