linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jay Fang <f.fangjian@huawei.com>
To: <broonie@kernel.org>
Cc: <linux-spi@vger.kernel.org>, <huangdaode@huawei.com>
Subject: [PATCH 04/11] spi: omap-100k: Fix checkpatch spacing errors
Date: Wed, 24 Mar 2021 14:16:35 +0800	[thread overview]
Message-ID: <1616566602-13894-5-git-send-email-f.fangjian@huawei.com> (raw)
In-Reply-To: <1616566602-13894-1-git-send-email-f.fangjian@huawei.com>

Fix checkpatch errors:

  ERROR: space prohibited before that ',' (ctx:WxW)
  #113: FILE: spi-omap-100k.c:113:
  +	writew(data , spi100k->base + SPI_TX_MSB);
 	            ^
  ERROR: space prohibited before that ',' (ctx:WxW)
  #249: FILE: spi-omap-100k.c:249:
  +	writew(0x3e , spi100k->base + SPI_SETUP1);
 	            ^
  ERROR: space prohibited before that ',' (ctx:WxW)
  #250: FILE: spi-omap-100k.c:250:
  +	writew(0x00 , spi100k->base + SPI_STATUS);
 	            ^
  ERROR: space prohibited before that ',' (ctx:WxW)
  #251: FILE: spi-omap-100k.c:251:
  +	writew(0x3e , spi100k->base + SPI_CTRL);
 	            ^

Signed-off-by: Jay Fang <f.fangjian@huawei.com>
---
 drivers/spi/spi-omap-100k.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/drivers/spi/spi-omap-100k.c b/drivers/spi/spi-omap-100k.c
index 36a4922..189fd2d 100644
--- a/drivers/spi/spi-omap-100k.c
+++ b/drivers/spi/spi-omap-100k.c
@@ -110,7 +110,7 @@ static void spi100k_write_data(struct spi_master *master, int len, int data)
 	}
 
 	spi100k_enable_clock(master);
-	writew(data , spi100k->base + SPI_TX_MSB);
+	writew(data, spi100k->base + SPI_TX_MSB);
 
 	writew(SPI_CTRL_SEN(0) |
 	       SPI_CTRL_WORD_SIZE(len) |
@@ -246,9 +246,9 @@ static int omap1_spi100k_setup_transfer(struct spi_device *spi,
 	cs->word_len = word_len;
 
 	/* SPI init before transfer */
-	writew(0x3e , spi100k->base + SPI_SETUP1);
-	writew(0x00 , spi100k->base + SPI_STATUS);
-	writew(0x3e , spi100k->base + SPI_CTRL);
+	writew(0x3e, spi100k->base + SPI_SETUP1);
+	writew(0x00, spi100k->base + SPI_STATUS);
+	writew(0x3e, spi100k->base + SPI_CTRL);
 
 	return 0;
 }
-- 
2.7.4


  parent reply	other threads:[~2021-03-24  6:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-24  6:16 [PATCH 00/11] spi: Fix ERRORs reported by checkpatch Jay Fang
2021-03-24  6:16 ` [PATCH 01/11] spi: spi-topcliff-pch: Fix checkpatch spacing error Jay Fang
2021-03-24  6:16 ` [PATCH 02/11] spi: sprd: " Jay Fang
2021-03-24  6:16 ` [PATCH 03/11] spi: pxa2xx: Fix checkpatch spacing errors Jay Fang
2021-03-24  6:16 ` Jay Fang [this message]
2021-03-24  6:16 ` [PATCH 05/11] spi: spi-mtk-nor: Fix checkpatch spacing error Jay Fang
2021-03-24  6:16 ` [PATCH 06/11] spi: dln2: Fix open brace following function definitions go on the next line Jay Fang
2021-03-24  6:16 ` [PATCH 07/11] spi: spi-bitbang: " Jay Fang
2021-03-24  6:16 ` [PATCH 08/11] spi: jcore: Fix trailing statements should be on " Jay Fang
2021-03-24  6:16 ` [PATCH 09/11] spi: spi-mem: Fix code indent should use tabs where possible Jay Fang
2021-03-24  6:16 ` [PATCH 10/11] spi: rockchip: " Jay Fang
2021-03-24  6:16 ` [PATCH 11/11] spi: pl022: Fix trailing whitespace Jay Fang
2021-03-24 23:39 ` [PATCH 00/11] spi: Fix ERRORs reported by checkpatch Mark Brown

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=1616566602-13894-5-git-send-email-f.fangjian@huawei.com \
    --to=f.fangjian@huawei.com \
    --cc=broonie@kernel.org \
    --cc=huangdaode@huawei.com \
    --cc=linux-spi@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).