From: Eli Lindsey <eli@siliconsprawl.com>
To: gregkh@suse.de, d@teklibre.com
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Eli Lindsey <eli@siliconsprawl.com>
Subject: [PATCH 1/4] staging: frontier: fix extra spaces in tranzport.c
Date: Tue, 9 Mar 2010 00:15:30 -0600 [thread overview]
Message-ID: <1268115333-7971-1-git-send-email-eli@siliconsprawl.com> (raw)
This is a patch to tranzport.c that removes two cases of unnecessary whitespace
before a quoted newline found by the checkpatch.pl tool
Signed-off-by: Eli Lindsey <eli@siliconsprawl.com>
---
drivers/staging/frontier/tranzport.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/frontier/tranzport.c b/drivers/staging/frontier/tranzport.c
index 2f03f43..1f91001 100644
--- a/drivers/staging/frontier/tranzport.c
+++ b/drivers/staging/frontier/tranzport.c
@@ -255,7 +255,7 @@ static void usb_tranzport_interrupt_in_callback(struct urb *urb)
if (urb->actual_length != 8) {
dev_warn(&dev->intf->dev,
"Urb length was %d bytes!!"
- "Do something intelligent \n",
+ "Do something intelligent\n",
urb->actual_length);
} else {
dbg_info(&dev->intf->dev,
@@ -724,7 +724,7 @@ static ssize_t usb_tranzport_write(struct file *file,
}
if (dev->interrupt_out_endpoint == NULL) {
- err("Endpoint should not be be null! \n");
+ err("Endpoint should not be be null!\n");
goto unlock_exit;
}
--
1.6.3.3
next reply other threads:[~2010-03-09 6:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 6:15 Eli Lindsey [this message]
2010-03-09 6:15 ` [PATCH 2/4] staging: frontier: fix extra spaces in alphatrack.c Eli Lindsey
2010-03-09 6:15 ` [PATCH 3/4] staging: frontier: switch to strict_strtoul in tranzport.c Eli Lindsey
2010-03-09 6:15 ` [PATCH 4/4] staging: frontier: switch semaphores to mutexes Eli Lindsey
2010-04-08 20:21 ` [PATCH 2/4] staging: frontier: fix extra spaces in alphatrack.c Greg KH
2010-04-08 20:20 ` [PATCH 1/4] staging: frontier: fix extra spaces in tranzport.c Greg KH
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=1268115333-7971-1-git-send-email-eli@siliconsprawl.com \
--to=eli@siliconsprawl.com \
--cc=d@teklibre.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@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
Powered by JetHome