spi: Don't break user-visible strings to multiple source lines in drivers

User-visible strings are more difficult to grep from sources if they are
separated to multiple source lines. This is worse than over 80 columns long
line code style violation.

Fix this by making those to single-line strings or by breaking them between
variables.

While at there, convert if (printk_ratelimit()) dev_warn() to use
dev_warn_ratelimited in spi-pxa2xx.c.

Signed-off-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Signed-off-by: Mark Brown <broonie@linaro.org>

1 files changed, 7 insertions, 6 deletions

diff --git a/drivers/spi/spi-topcliff-pch.c b/drivers/spi/spi-topcliff-pch.c
index eaeeed51bbbf..14843efaaf3a 100644
--- a/drivers/spi/spi-topcliff-pch.c
+++ b/drivers/spi/spi-topcliff-pch.c
@@ -506,8 +506,8 @@ static int pch_spi_transfer(struct spi_device *pspi, struct spi_message *pmsg)
                 goto err_out;
         }
 
-        dev_dbg(&pspi->dev, "%s Transfer List not empty. "
-                "Transfer Speed is set.\n", __func__);
+        dev_dbg(&pspi->dev,
+                "%s Transfer List not empty. Transfer Speed is set.\n", __func__);
 
         spin_lock_irqsave(&data->lock, flags);
         /* validate Tx/Rx buffers and Transfer length */
@@ -526,8 +526,9 @@ static int pch_spi_transfer(struct spi_device *pspi, struct spi_message *pmsg)
                         goto err_return_spinlock;
                 }
 
-                dev_dbg(&pspi->dev, "%s Tx/Rx buffer valid. Transfer length"
-                        " valid\n", __func__);
+                dev_dbg(&pspi->dev,
+                        "%s Tx/Rx buffer valid. Transfer length valid\n",
+                        __func__);
 
                 /* if baud rate has been specified validate the same */
                 if (transfer->speed_hz > PCH_MAX_BAUDRATE)
@@ -1181,8 +1182,8 @@ static void pch_spi_process_messages(struct work_struct *pwork)
         spin_lock(&data->lock);
         /* check if suspend has been initiated;if yes flush queue */
         if (data->board_dat->suspend_sts || (data->status == STATUS_EXITING)) {
-                dev_dbg(&data->master->dev, "%s suspend/remove initiated,"
-                        "flushing queue\n", __func__);
+                dev_dbg(&data->master->dev,
+                        "%s suspend/remove initiated, flushing queue\n", __func__);
                 list_for_each_entry_safe(pmsg, tmp, data->queue.next, queue) {
                         pmsg->status = -EIO;