From: Juston Li <juston.h.li@gmail.com>
To: sudipm.mukherjee@gmail.com, teddy.wang@siliconmotion.com,
gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Juston Li <juston.h.li@gmail.com>
Subject: [PATCH v5 05/19] staging: sm750fb: remove space between function name and parenthesis
Date: Wed, 15 Jul 2015 04:14:34 +0000 [thread overview]
Message-ID: <1436933688-5408-5-git-send-email-juston.h.li@gmail.com> (raw)
In-Reply-To: <CAFow2F9-0W4VRjLHmXZuv2vCwyGYRDatbCOrmg5o-AY0-nb-dw@mail.gmail.com>
Fixes checkpatch.pl warning:
WARNING: space prohibited between function name and open parenthesis '('
Signed-off-by: Juston Li <juston.h.li@gmail.com>
---
drivers/staging/sm750fb/sm750_accel.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/sm750fb/sm750_accel.c b/drivers/staging/sm750fb/sm750_accel.c
index 73d84de..982cf1e 100644
--- a/drivers/staging/sm750fb/sm750_accel.c
+++ b/drivers/staging/sm750fb/sm750_accel.c
@@ -278,11 +278,11 @@ unsigned int rop2) /* ROP value */
{
write_dpr(accel, DE_SOURCE,
- FIELD_SET (0, DE_SOURCE, WRAP, DISABLE) |
+ FIELD_SET(0, DE_SOURCE, WRAP, DISABLE) |
FIELD_VALUE(0, DE_SOURCE, X_K1, sx) |
FIELD_VALUE(0, DE_SOURCE, Y_K2, sy)); /* dpr0 */
write_dpr(accel, DE_DESTINATION,
- FIELD_SET (0, DE_DESTINATION, WRAP, DISABLE) |
+ FIELD_SET(0, DE_DESTINATION, WRAP, DISABLE) |
FIELD_VALUE(0, DE_DESTINATION, X, dx) |
FIELD_VALUE(0, DE_DESTINATION, Y, dy)); /* dpr04 */
write_dpr(accel, DE_DIMENSION,
@@ -390,11 +390,11 @@ int hw_imageblit(struct lynx_accel *accel,
/* Note: For 2D Source in Host Write, only X_K1_MONO field is needed, and Y_K2 field is not used.
For mono bitmap, use startBit for X_K1. */
write_dpr(accel, DE_SOURCE,
- FIELD_SET (0, DE_SOURCE, WRAP, DISABLE) |
+ FIELD_SET(0, DE_SOURCE, WRAP, DISABLE) |
FIELD_VALUE(0, DE_SOURCE, X_K1_MONO, startBit)); /* dpr00 */
write_dpr(accel, DE_DESTINATION,
- FIELD_SET (0, DE_DESTINATION, WRAP, DISABLE) |
+ FIELD_SET(0, DE_DESTINATION, WRAP, DISABLE) |
FIELD_VALUE(0, DE_DESTINATION, X, dx) |
FIELD_VALUE(0, DE_DESTINATION, Y, dy)); /* dpr04 */
--
2.4.5
next prev parent reply other threads:[~2015-07-15 4:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 4:10 [PATCH v5 00/19] staging: sm750fb: checkpatch.pl fixes Juston Li
2015-07-15 4:14 ` [PATCH v5 01/19] staging: sm750fb: use tabs for indentation Juston Li
2015-07-15 4:14 ` [PATCH v5 02/19] staging: sm750fb: remove spacing after open parenthesis Juston Li
2015-07-15 4:14 ` [PATCH v5 03/19] staging: sm750fb: remove space before close parenthesis Juston Li
2015-07-15 4:14 ` [PATCH v5 04/19] staging: sm750fb: add space before open parenthesis Juston Li
2015-07-15 4:14 ` Juston Li [this message]
2015-07-15 4:14 ` [PATCH v5 06/19] staging: sm750fb: add space before open brace Juston Li
2015-07-15 4:14 ` [PATCH v5 07/19] staging: sm750fb: add space after close brace Juston Li
2015-07-15 4:14 ` [PATCH v5 08/19] staging: sm750fb: add space after enum definition Juston Li
2015-07-15 4:14 ` [PATCH v5 09/19] staging: sm750fb: add space after struct definition Juston Li
2015-07-15 4:14 ` [PATCH v5 10/19] staging: sm750fb: add space after return type Juston Li
2015-07-15 4:14 ` [PATCH v5 11/19] staging: sm750fb: consistent spacing around operators Juston Li
2015-07-15 4:14 ` [PATCH v5 12/19] staging: sm750fb: add spaces " Juston Li
2015-07-15 4:14 ` [PATCH v5 13/19] staging: sm750fb: add space after semicolon Juston Li
2015-07-15 4:14 ` [PATCH v5 14/19] staging: sm750fb: remove trailing whitespace Juston Li
2015-07-15 4:14 ` [PATCH v5 15/19] staging: sm750fb: remove unnecessary whitespace Juston Li
2015-07-15 4:14 ` [PATCH v5 16/19] staging: sm750fb: fix brace placement Juston Li
2015-07-15 4:14 ` [PATCH v5 17/19] staging: sm750fb: move while to follow do close brace Juston Li
2015-07-15 4:14 ` [PATCH v5 18/19] staging: sm750fb: remove unnecessary braces Juston Li
2015-07-15 4:14 ` [PATCH v5 19/19] staging: sm750fb: add missing blank line after declarations Juston Li
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=1436933688-5408-5-git-send-email-juston.h.li@gmail.com \
--to=juston.h.li@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=teddy.wang@siliconmotion.com \
/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;
as well as URLs for NNTP newsgroup(s).