public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sangho Yi <antiroot@gmail.com>
To: devel@driverdev.osuosl.org
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	Sangho Yi <antiroot@gmail.com>
Subject: [PATCH 05/14] staging: csr: Removed spaces between ( and arguments and ) on io.c
Date: Tue, 16 Oct 2012 02:24:24 +0900	[thread overview]
Message-ID: <1350321868-2613-5-git-send-email-antiroot@gmail.com> (raw)
In-Reply-To: <1350321868-2613-1-git-send-email-antiroot@gmail.com>

I found many coding style errors including spaces like this:
foo ( arg );
So, I fixed them as follows->   foo (arg);

Signed-off-by: Sangho Yi <antiroot@gmail.com>
---
 drivers/staging/csr/io.c |   16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/drivers/staging/csr/io.c b/drivers/staging/csr/io.c
index 6f89556..ed34914 100644
--- a/drivers/staging/csr/io.c
+++ b/drivers/staging/csr/io.c
@@ -349,7 +349,7 @@ register_unifi_sdio(CsrSdioFunction *sdio_dev, int bus_id, struct device *dev)
 		priv->totalInterfaceCount =0;
 
 		for(i=1;i<CSR_WIFI_NUM_INTERFACES;i++) {
-			if( !uf_alloc_netdevice_for_other_interfaces(priv,i) ) {
+			if(!uf_alloc_netdevice_for_other_interfaces(priv,i)) {
 				/* error occured while allocating the
 				 * net_device for interface[i].
 				 * The net_device are allocated for the
@@ -896,7 +896,7 @@ uf_read_proc(char *page, char **start, off_t offset, int count,
 		return 0;
 	}
 
-	p = kmalloc( UNIFI_DEBUG_TXT_BUFFER, GFP_KERNEL );
+	p = kmalloc(UNIFI_DEBUG_TXT_BUFFER, GFP_KERNEL);
 
 	orig_p = p;
 
@@ -953,24 +953,24 @@ uf_read_proc(char *page, char **start, off_t offset, int count,
 
 	written = UNIFI_DEBUG_TXT_BUFFER - remain;
 
-	if( offset >= written ) {
+	if(offset >= written) {
 		*eof = 1;
-		kfree( orig_p );
+		kfree(orig_p);
 		return(0);
 	}
 
-	if( offset + count > written ) {
+	if(offset + count > written) {
 		actual_amount_to_copy = written - offset;
 		*eof = 1;
 	} else {
 		actual_amount_to_copy = count;
 	}
 
-	memcpy( page, &(orig_p[offset]), actual_amount_to_copy );
+	memcpy(page, &(orig_p[offset]), actual_amount_to_copy);
 
-	kfree( orig_p );
+	kfree(orig_p);
 
-	return( actual_amount_to_copy );
+	return(actual_amount_to_copy);
 } /* uf_read_proc() */
 #endif
 
-- 
1.7.9.5


  parent reply	other threads:[~2012-10-15 17:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-15 17:24 [PATCH 01/14] staging: csr: fixed indentation from spaces to tabs on io.c Sangho Yi
2012-10-15 17:24 ` [PATCH 02/14] staging: csr: Fixed exceeding 80 chars per line problems " Sangho Yi
2012-10-15 17:24 ` [PATCH 03/14] staging: csr: Removed trailing whitespaces " Sangho Yi
2012-10-15 17:24 ` [PATCH 04/14] staging: csr: Fixed the positions of the opening braces { " Sangho Yi
2012-10-15 17:24 ` Sangho Yi [this message]
2012-10-15 17:24 ` [PATCH 06/14] staging: csr: Added whitespaces around comma, =, >, <, ; (mostly for loops) Sangho Yi
2012-10-15 17:24 ` [PATCH 07/14] staging: csr: Fixed indentation mistakes on io.c Sangho Yi
2012-10-15 17:24 ` [PATCH 08/14] staging: csr: Removed unnecessary whitespace before newline " Sangho Yi
2012-10-15 17:24 ` [PATCH 09/14] staging: csr: Fixed foo * bar --> foo *bar " Sangho Yi
2012-10-18 13:40 ` [PATCH 01/14] staging: csr: fixed indentation from spaces to tabs " Dan Carpenter
2012-10-22 21:04   ` 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=1350321868-2613-5-git-send-email-antiroot@gmail.com \
    --to=antiroot@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --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