linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: hanyu001@208suo.com
To: benh@kernel.crashing.org, mpe@ellerman.id.au, npiggin@gmail.com,
	christophe.leroy@csgroup.eu, windhl@126.com
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH] platforms: powermac: insert space before the open parenthesis '('
Date: Tue, 18 Jul 2023 17:48:59 +0800	[thread overview]
Message-ID: <a475a9b5702e1044296209daec102e69@208suo.com> (raw)
In-Reply-To: <tencent_EA51887C68AF6A7DCE5504EAAB3F2AB5C609@qq.com>

Fixes checkpatch errors:

/platforms/powermac/low_i2c.c:55:ERROR: space required before the open 
parenthesis '('
/platforms/powermac/low_i2c.c:63:ERROR: space required before the open 
parenthesis '('

Signed-off-by: Yu Han <hanyu001@208suo.com>
---
  arch/powerpc/platforms/powermac/low_i2c.c | 4 ++--
  1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/powerpc/platforms/powermac/low_i2c.c 
b/arch/powerpc/platforms/powermac/low_i2c.c
index 40f3aa432fba..25cc6eec962f 100644
--- a/arch/powerpc/platforms/powermac/low_i2c.c
+++ b/arch/powerpc/platforms/powermac/low_i2c.c
@@ -52,7 +52,7 @@
  #ifdef DEBUG
  #define DBG(x...) do {\
          printk(KERN_DEBUG "low_i2c:" x);    \
-    } while(0)
+    } while (0)
  #else
  #define DBG(x...)
  #endif
@@ -60,7 +60,7 @@
  #ifdef DEBUG_LOW
  #define DBG_LOW(x...) do {\
          printk(KERN_DEBUG "low_i2c:" x);    \
-    } while(0)
+    } while (0)
  #else
  #define DBG_LOW(x...)
  #endif

       reply	other threads:[~2023-07-18  9:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tencent_EA51887C68AF6A7DCE5504EAAB3F2AB5C609@qq.com>
2023-07-18  9:48 ` hanyu001 [this message]
     [not found] <tencent_3EB579E7E40217D5639568E3324407B49E08@qq.com>
2023-07-18  9:37 ` [PATCH] platforms: powermac: insert space before the open parenthesis '(' 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=a475a9b5702e1044296209daec102e69@208suo.com \
    --to=hanyu001@208suo.com \
    --cc=benh@kernel.crashing.org \
    --cc=christophe.leroy@csgroup.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=windhl@126.com \
    /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).