All of lore.kernel.org
 help / color / mirror / Atom feed
From: hanyu001@208suo.com
To: James.Bottomley@HansenPartnership.com, deller@gmx.de
Cc: linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] parisc: kernel:  "foo * bar" should be "foo *bar"
Date: Thu, 20 Jul 2023 14:14:30 +0800	[thread overview]
Message-ID: <dbc24737ba923daee7d3b948cc028dc3@208suo.com> (raw)
In-Reply-To: <tencent_2E6F87E6BC1B92D422B02265685D90AFAD06@qq.com>

This patch fixes the checkpatch.pl error

./arch/parisc/kernel/sys_parisc32.c:29: ERROR: "foo * bar" should be 
"foo *bar"

Signed-off-by: Yu Han <hanyu001@208suo.com>
---
  arch/parisc/kernel/sys_parisc32.c | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/parisc/kernel/sys_parisc32.c 
b/arch/parisc/kernel/sys_parisc32.c
index 2a12a54..abe87d2 100644
--- a/arch/parisc/kernel/sys_parisc32.c
+++ b/arch/parisc/kernel/sys_parisc32.c
@@ -26,7 +26,7 @@ asmlinkage long sys32_unimplemented(int r26, int r25, 
int r24, int r23,

  asmlinkage long sys32_fanotify_mark(compat_int_t fanotify_fd, 
compat_uint_t flags,
      compat_uint_t mask0, compat_uint_t mask1, compat_int_t dfd,
-    const char  __user * pathname)
+    const char  __user *pathname)
  {
      return sys_fanotify_mark(fanotify_fd, flags,
              ((__u64)mask1 << 32) | mask0,

       reply	other threads:[~2023-07-20  6:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tencent_2E6F87E6BC1B92D422B02265685D90AFAD06@qq.com>
2023-07-20  6:14 ` hanyu001 [this message]
     [not found] <tencent_30B748128B938A55A13C4143B6101D6BF308@qq.com>
2023-07-20  6:21 ` [PATCH] parisc: kernel: "foo * bar" should be "foo *bar" hanyu001

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=dbc24737ba923daee7d3b948cc028dc3@208suo.com \
    --to=hanyu001@208suo.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=deller@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.