linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: wuyonggang001@208suo.com
To: viro@zeniv.linux.org.uk, brauner@kernel.org
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] fs/filesystems.c: ERROR: "(foo*)" should be "(foo *)"
Date: Mon, 17 Jul 2023 15:07:11 +0800	[thread overview]
Message-ID: <a456720721d2f8fc33bb0befbe2ad115@208suo.com> (raw)
In-Reply-To: <20230717070500.38410-1-zhanglibing@cdjrlc.com>

Fix five occurrences of the checkpatch.pl error:
ERROR: "(foo*)" should be "(foo *)"

Signed-off-by: Yonggang Wu <wuyonggang001@208suo.com>
---
  fs/filesystems.c | 20 ++++++++++----------
  1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/fs/filesystems.c b/fs/filesystems.c
index 58b9067b2391..6a93b4904d27 100644
--- a/fs/filesystems.c
+++ b/fs/filesystems.c
@@ -69,10 +69,10 @@ static struct file_system_type 
**find_filesystem(const char *name, unsigned len)
   *    unregistered.
   */

-int register_filesystem(struct file_system_type * fs)
+int register_filesystem(struct file_system_type *fs)
  {
      int res = 0;
-    struct file_system_type ** p;
+    struct file_system_type **p;

      if (fs->parameters &&
          !fs_validate_description(fs->name, fs->parameters))
@@ -105,9 +105,9 @@ EXPORT_SYMBOL(register_filesystem);
   *    may be freed or reused.
   */

-int unregister_filesystem(struct file_system_type * fs)
+int unregister_filesystem(struct file_system_type *fs)
  {
-    struct file_system_type ** tmp;
+    struct file_system_type **tmp;

      write_lock(&file_systems_lock);
      tmp = &file_systems;
@@ -129,9 +129,9 @@ int unregister_filesystem(struct file_system_type * 
fs)
  EXPORT_SYMBOL(unregister_filesystem);

  #ifdef CONFIG_SYSFS_SYSCALL
-static int fs_index(const char __user * __name)
+static int fs_index(const char __user *__name)
  {
-    struct file_system_type * tmp;
+    struct file_system_type *tmp;
      struct filename *name;
      int err, index;

@@ -153,9 +153,9 @@ static int fs_index(const char __user * __name)
      return err;
  }

-static int fs_name(unsigned int index, char __user * buf)
+static int fs_name(unsigned int index, char __user *buf)
  {
-    struct file_system_type * tmp;
+    struct file_system_type *tmp;
      int len, res;

      read_lock(&file_systems_lock);
@@ -175,7 +175,7 @@ static int fs_name(unsigned int index, char __user * 
buf)

  static int fs_maxindex(void)
  {
-    struct file_system_type * tmp;
+    struct file_system_type *tmp;
      int index;

      read_lock(&file_systems_lock);
@@ -236,7 +236,7 @@ int __init list_bdev_fs_names(char *buf, size_t 
size)
  #ifdef CONFIG_PROC_FS
  static int filesystems_proc_show(struct seq_file *m, void *v)
  {
-    struct file_system_type * tmp;
+    struct file_system_type *tmp;

      read_lock(&file_systems_lock);
      tmp = file_systems;

       reply	other threads:[~2023-07-17  7:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230717070500.38410-1-zhanglibing@cdjrlc.com>
2023-07-17  7:07 ` wuyonggang001 [this message]
2023-07-19  6:14   ` [PATCH] fs/filesystems.c: ERROR: "(foo*)" should be "(foo *)" Christian Brauner

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=a456720721d2f8fc33bb0befbe2ad115@208suo.com \
    --to=wuyonggang001@208suo.com \
    --cc=brauner@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).