LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jingyu Wang <jingyuwang_vip@163.com>
To: mpe@ellerman.id.au, npiggin@gmail.com, christophe.leroy@csgroup.eu
Cc: Jingyu Wang <jingyuwang_vip@163.com>,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH] powerpc: remove redundant space
Date: Tue,  6 Sep 2022 23:32:55 +0800	[thread overview]
Message-ID: <20220906153255.6688-1-jingyuwang_vip@163.com> (raw)

This commit remmove redundant space in arch/powerpc/sysdev/mmio_nvram.c

Signed-off-by: Jingyu Wang <jingyuwang_vip@163.com>
---
 arch/powerpc/sysdev/mmio_nvram.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/arch/powerpc/sysdev/mmio_nvram.c b/arch/powerpc/sysdev/mmio_nvram.c
index eb48210ef98e..cc15b161ada6 100644
--- a/arch/powerpc/sysdev/mmio_nvram.c
+++ b/arch/powerpc/sysdev/mmio_nvram.c
@@ -35,7 +35,7 @@ static ssize_t mmio_nvram_read(char *buf, size_t count, loff_t *index)
 	memcpy_fromio(buf, mmio_nvram_start + *index, count);
 
 	spin_unlock_irqrestore(&mmio_nvram_lock, flags);
-	
+
 	*index += count;
 	return count;
 }
@@ -71,7 +71,7 @@ static ssize_t mmio_nvram_write(char *buf, size_t count, loff_t *index)
 	memcpy_toio(mmio_nvram_start + *index, buf, count);
 
 	spin_unlock_irqrestore(&mmio_nvram_lock, flags);
-	
+
 	*index += count;
 	return count;
 }
@@ -117,7 +117,7 @@ int __init mmio_nvram_init(void)
 	}
 	nvram_addr = r.start;
 	mmio_nvram_len = resource_size(&r);
-	if ( (!mmio_nvram_len) || (!nvram_addr) ) {
+	if ((!mmio_nvram_len) || (!nvram_addr)) {
 		printk(KERN_WARNING "nvram: address or length is 0\n");
 		ret = -EIO;
 		goto out;

base-commit: e47eb90a0a9ae20b82635b9b99a8d0979b757ad8
-- 
2.34.1


             reply	other threads:[~2022-09-06 21:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-06 15:32 Jingyu Wang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-03-03 11:57 [PATCH] powerpc: remove redundant space maqiang
2021-03-03 21:33 ` Christophe Leroy

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=20220906153255.6688-1-jingyuwang_vip@163.com \
    --to=jingyuwang_vip@163.com \
    --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 \
    /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