linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: huzhi001@208suo.com
To: dsterba@suse.com
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] VFS: Fix seven errors in bitmap.c
Date: Fri, 14 Jul 2023 15:14:18 +0800	[thread overview]
Message-ID: <80ff0222e0fc0b8e25ae4837b76bce2d@208suo.com> (raw)
In-Reply-To: <tencent_CE461BFFDACFEA943A778650FB672D9E3207@qq.com>

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)

Signed-off-by: ZhiHu <huzhi001@208suo.com>
---
  fs/affs/bitmap.c | 8 ++++----
  1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/fs/affs/bitmap.c b/fs/affs/bitmap.c
index 5ba9ef2742f6..b1620b6ff8a9 100644
--- a/fs/affs/bitmap.c
+++ b/fs/affs/bitmap.c
@@ -87,19 +87,19 @@ affs_free_block(struct super_block *sb, u32 block)
      return;

  err_free:
-    affs_warning(sb,"affs_free_block","Trying to free block %u which is 
already free", block);
+    affs_warning(sb, "affs_free_block", "Trying to free block %u which 
is already free", block);
      mutex_unlock(&sbi->s_bmlock);
      return;

  err_bh_read:
-    affs_error(sb,"affs_free_block","Cannot read bitmap block %u", 
bm->bm_key);
+    affs_error(sb, "affs_free_block", "Cannot read bitmap block %u", 
bm->bm_key);
      sbi->s_bmap_bh = NULL;
      sbi->s_last_bmap = ~0;
      mutex_unlock(&sbi->s_bmlock);
      return;

  err_range:
-    affs_error(sb, "affs_free_block","Block %u outside partition", 
block);
+    affs_error(sb, "affs_free_block", "Block %u outside partition", 
block);
  }

  /*
@@ -232,7 +232,7 @@ affs_alloc_block(struct inode *inode, u32 goal)
      return blk;

  err_bh_read:
-    affs_error(sb,"affs_read_block","Cannot read bitmap block %u", 
bm->bm_key);
+    affs_error(sb, "affs_read_block", "Cannot read bitmap block %u", 
bm->bm_key);
      sbi->s_bmap_bh = NULL;
      sbi->s_last_bmap = ~0;
  err_full:

       reply	other threads:[~2023-07-14  7:14 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 ` huzhi001 [this message]
2023-07-14 10:46   ` [PATCH] VFS: Fix seven errors in bitmap.c David Sterba

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=80ff0222e0fc0b8e25ae4837b76bce2d@208suo.com \
    --to=huzhi001@208suo.com \
    --cc=dsterba@suse.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).