From: Johan Meiring <johanmeiring@gmail.com>
To: gregkh@linuxfoundation.org, a.beregalov@gmail.com,
devendra.aaru@gmail.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Cc: Johan Meiring <johanmeiring@gmail.com>
Subject: [PATCH 09/10] staging: cxt1e1: sbecrc.c: fixes coding style issue
Date: Tue, 20 Nov 2012 19:28:51 +0200 [thread overview]
Message-ID: <1353432532-21203-9-git-send-email-johanmeiring@gmail.com> (raw)
In-Reply-To: <1353432532-21203-1-git-send-email-johanmeiring@gmail.com>
This commit sorts out a coding style issue related to spaces between
parentheses and function names.
Signed-off-by: Johan Meiring <johanmeiring@gmail.com>
---
drivers/staging/cxt1e1/sbecrc.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/cxt1e1/sbecrc.c b/drivers/staging/cxt1e1/sbecrc.c
index f95728e..87512a5 100644
--- a/drivers/staging/cxt1e1/sbecrc.c
+++ b/drivers/staging/cxt1e1/sbecrc.c
@@ -44,7 +44,7 @@ static u_int32_t CRCTable[CRC_TABLE_ENTRIES];
***************************************************************************/
static void
-genCrcTable (u_int32_t *CRCTable)
+genCrcTable(u_int32_t *CRCTable)
{
int ii, jj;
u_int32_t crc;
@@ -83,7 +83,7 @@ genCrcTable (u_int32_t *CRCTable)
*/
void
-sbeCrc (u_int8_t *buffer, /* data buffer to crc */
+sbeCrc(u_int8_t *buffer, /* data buffer to crc */
u_int32_t count, /* length of block in bytes */
u_int32_t initialCrc, /* starting CRC */
u_int32_t *result)
@@ -99,15 +99,15 @@ sbeCrc (u_int8_t *buffer, /* data buffer to crc */
if (!crcTableInit) {
#ifdef STATIC_CRC_TABLE
tbl = &CRCTable;
- genCrcTable (tbl);
+ genCrcTable(tbl);
#else
- tbl = (u_int32_t *) OS_kmalloc (CRC_TABLE_ENTRIES * sizeof (u_int32_t));
+ tbl = (u_int32_t *) OS_kmalloc(CRC_TABLE_ENTRIES * sizeof(u_int32_t));
if (tbl == 0) {
*result = 0; /* dummy up return value due to malloc
* failure */
return;
}
- genCrcTable (tbl);
+ genCrcTable(tbl);
#endif
}
/* inverting bits makes ZMODEM & PKZIP compatible */
@@ -125,7 +125,7 @@ sbeCrc (u_int8_t *buffer, /* data buffer to crc */
#ifndef STATIC_CRC_TABLE
crcTableInit = 0;
- OS_kfree (tbl);
+ OS_kfree(tbl);
#endif
}
--
1.7.10.4
next prev parent reply other threads:[~2012-11-20 17:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 17:28 [PATCH 01/10] staging: cxt1e1: musycc.h: fixes indentation issues Johan Meiring
2012-11-20 17:28 ` [PATCH 02/10] staging: cxt1e1: musycc.h: fixes coding style issues Johan Meiring
2012-11-20 17:28 ` [PATCH 03/10] staging: cxt1e1: musycc.h: fixes brace placement Johan Meiring
2012-11-20 17:28 ` [PATCH 04/10] staging: cxt1e1: musycc.c: uses tabs for indentation Johan Meiring
2012-11-20 17:28 ` [PATCH 05/10] staging: cxt1e1: musycc.c: fixes brace placement Johan Meiring
2012-11-20 17:28 ` [PATCH 06/10] staging: cxt1e1: musycc.c: fixes placement of parentheses Johan Meiring
2012-11-21 9:07 ` Dan Carpenter
2012-11-20 17:28 ` [PATCH 07/10] staging: cxt1e1: sbecrc.c: fixes indentation issues Johan Meiring
2012-11-20 17:28 ` [PATCH 08/10] staging: cxt1e1: sbecrc.c: fixes brace placement Johan Meiring
2012-11-20 17:28 ` Johan Meiring [this message]
2012-11-20 17:28 ` [PATCH 10/10] staging: cxt1e1: sbecrc.c: fixes 80+ char line length issue Johan Meiring
2012-11-21 9:04 ` Dan Carpenter
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=1353432532-21203-9-git-send-email-johanmeiring@gmail.com \
--to=johanmeiring@gmail.com \
--cc=a.beregalov@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=devendra.aaru@gmail.com \
--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