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 03/11] spi: pxa2xx: Fix checkpatch spacing errors
Date: Wed, 24 Mar 2021 14:16:34 +0800	[thread overview]
Message-ID: <1616566602-13894-4-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)
  #255: FILE: spi-pxa2xx-pci.c:255:
  +	ssp->clk = clk_register_fixed_rate(&dev->dev, buf , NULL, 0,
 	                                                  ^
  ERROR: "foo* bar" should be "foo *bar"
  #621: FILE: spi-pxa2xx.c:621:
  +static void int_error_stop(struct driver_data *drv_data, const char* msg)

Signed-off-by: Jay Fang <f.fangjian@huawei.com>
---
 drivers/spi/spi-pxa2xx-pci.c | 2 +-
 drivers/spi/spi-pxa2xx.c     | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/spi/spi-pxa2xx-pci.c b/drivers/spi/spi-pxa2xx-pci.c
index 14fc41e..1833f58 100644
--- a/drivers/spi/spi-pxa2xx-pci.c
+++ b/drivers/spi/spi-pxa2xx-pci.c
@@ -252,7 +252,7 @@ static int pxa2xx_spi_pci_probe(struct pci_dev *dev,
 	ssp->irq = pci_irq_vector(dev, 0);
 
 	snprintf(buf, sizeof(buf), "pxa2xx-spi.%d", ssp->port_id);
-	ssp->clk = clk_register_fixed_rate(&dev->dev, buf , NULL, 0,
+	ssp->clk = clk_register_fixed_rate(&dev->dev, buf, NULL, 0,
 					   c->max_clk_rate);
 	 if (IS_ERR(ssp->clk))
 		return PTR_ERR(ssp->clk);
diff --git a/drivers/spi/spi-pxa2xx.c b/drivers/spi/spi-pxa2xx.c
index 0cc7672..b83f325f 100644
--- a/drivers/spi/spi-pxa2xx.c
+++ b/drivers/spi/spi-pxa2xx.c
@@ -618,7 +618,7 @@ static void reset_sccr1(struct driver_data *drv_data)
 	pxa2xx_spi_write(drv_data, SSCR1, sccr1_reg);
 }
 
-static void int_error_stop(struct driver_data *drv_data, const char* msg)
+static void int_error_stop(struct driver_data *drv_data, const char *msg)
 {
 	/* Stop and reset SSP */
 	write_SSSR_CS(drv_data, drv_data->clear_sr);
-- 
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 ` Jay Fang [this message]
2021-03-24  6:16 ` [PATCH 04/11] spi: omap-100k: Fix checkpatch spacing errors Jay Fang
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-4-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).