All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: linux-kernel@vger.kernel.org
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>, linux-media@vger.kernel.org
Subject: [PATCH 3/4] [media] dibx000_common: Fix line continuation format
Date: Thu, 16 Nov 2017 07:27:28 -0800	[thread overview]
Message-ID: <448d510e69dcf7a9195e2d378ddb17724c456221.1510845910.git.joe@perches.com> (raw)
In-Reply-To: <cover.1510845910.git.joe@perches.com>

Line continuations with excess spacing causes unexpected output.

Signed-off-by: Joe Perches <joe@perches.com>
---
 drivers/media/dvb-frontends/dibx000_common.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/drivers/media/dvb-frontends/dibx000_common.c b/drivers/media/dvb-frontends/dibx000_common.c
index bc28184c7fb0..d981233e458f 100644
--- a/drivers/media/dvb-frontends/dibx000_common.c
+++ b/drivers/media/dvb-frontends/dibx000_common.c
@@ -288,8 +288,8 @@ static int dibx000_i2c_gated_gpio67_xfer(struct i2c_adapter *i2c_adap,
 	int ret;
 
 	if (num > 32) {
-		dprintk("%s: too much I2C message to be transmitted (%i).\
-				Maximum is 32", __func__, num);
+		dprintk("%s: too much I2C message to be transmitted (%i). Maximum is 32",
+			__func__, num);
 		return -ENOMEM;
 	}
 
@@ -335,8 +335,8 @@ static int dibx000_i2c_gated_tuner_xfer(struct i2c_adapter *i2c_adap,
 	int ret;
 
 	if (num > 32) {
-		dprintk("%s: too much I2C message to be transmitted (%i).\
-				Maximum is 32", __func__, num);
+		dprintk("%s: too much I2C message to be transmitted (%i). Maximum is 32",
+			__func__, num);
 		return -ENOMEM;
 	}
 
-- 
2.15.0

  parent reply	other threads:[~2017-11-16 15:28 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16 15:27 [PATCH 0/4] treewide: Fix line continuation formats Joe Perches
2017-11-16 15:27 ` Joe Perches
2017-11-16 15:27 ` Joe Perches
2017-11-16 15:27 ` [PATCH 1/4] rk3399_dmc: Fix line continuation format Joe Perches
2017-11-22  5:13   ` Chanwoo Choi
2017-11-22 10:41     ` Joe Perches
     [not found]     ` <CGME20171116152742epcas2p22b17887a4d7f2adcd3beb414988dbce3@epcms1p1>
2017-11-23  1:21       ` MyungJoo Ham
2017-11-23  1:21         ` MyungJoo Ham
2017-11-23  1:45         ` Chanwoo Choi
2017-11-23  2:07           ` Joe Perches
2017-11-23  2:12             ` Chanwoo Choi
2017-11-23  2:18               ` Joe Perches
2017-11-23  2:23                 ` Chanwoo Choi
2017-11-23  2:29                   ` Joe Perches
2017-11-23  2:35                     ` Chanwoo Choi
2017-11-23  2:38                       ` Joe Perches
2017-11-16 15:27 ` [PATCH 2/4] drm: amd: Fix line continuation formats Joe Perches
2017-11-16 15:27   ` Joe Perches
2017-11-16 15:38   ` Harry Wentland
2017-11-16 15:38     ` Harry Wentland
2017-11-16 15:50     ` Joe Perches
2017-11-16 15:50       ` Joe Perches
2017-11-17 19:52       ` Alex Deucher
2017-11-17 19:52         ` Alex Deucher
2017-11-16 15:27 ` Joe Perches [this message]
2017-11-16 15:27 ` [PATCH 4/4] ima: Fix line continuation format Joe Perches
2017-11-16 15:27   ` Joe Perches
2017-11-16 17:11 ` [PATCH 0/4] treewide: Fix line continuation formats Mimi Zohar
2017-11-16 17:11   ` Mimi Zohar
2017-11-16 17:11   ` Mimi Zohar
2017-11-16 17:17   ` Joe Perches
2017-11-16 17:17     ` Joe Perches
2017-11-16 19:35     ` Mimi Zohar
2017-11-16 19:35       ` Mimi Zohar

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=448d510e69dcf7a9195e2d378ddb17724c456221.1510845910.git.joe@perches.com \
    --to=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.