From: Youngdo Lee <paul.ydlee@gmail.com>
To: gregkh@linuxfoundation.org, thomas.petazzoni@free-electrons.com,
noralf@tronnes.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Youngdo Lee <paul.ydlee@gmail.com>
Subject: [PATCH] staging: fbtft: fbtft-bus.c: Fix checkpatch error
Date: Sat, 4 Feb 2017 13:42:48 +0900 [thread overview]
Message-ID: <1486183368-31664-1-git-send-email-paul.ydlee@gmail.com> (raw)
Fix checkpatch error:
ERROR: space prohibited before that close parenthesis ')'
Signed-off-by: Youngdo Lee <paul.ydlee@gmail.com>
---
drivers/staging/fbtft/fbtft-bus.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/fbtft/fbtft-bus.c b/drivers/staging/fbtft/fbtft-bus.c
index ec45043..3ce265d 100644
--- a/drivers/staging/fbtft/fbtft-bus.c
+++ b/drivers/staging/fbtft/fbtft-bus.c
@@ -10,6 +10,7 @@
*
*****************************************************************************/
+#define nop_modifier(expr) (expr)
#define define_fbtft_write_reg(func, type, modifier) \
void func(struct fbtft_par *par, int len, ...) \
{ \
@@ -68,9 +69,9 @@ void func(struct fbtft_par *par, int len, ...) \
} \
EXPORT_SYMBOL(func);
-define_fbtft_write_reg(fbtft_write_reg8_bus8, u8, )
+define_fbtft_write_reg(fbtft_write_reg8_bus8, u8, nop_modifier)
define_fbtft_write_reg(fbtft_write_reg16_bus8, u16, cpu_to_be16)
-define_fbtft_write_reg(fbtft_write_reg16_bus16, u16, )
+define_fbtft_write_reg(fbtft_write_reg16_bus16, u16, nop_modifier)
void fbtft_write_reg8_bus9(struct fbtft_par *par, int len, ...)
{
--
1.9.1
next reply other threads:[~2017-02-04 4:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-04 4:42 Youngdo Lee [this message]
2017-02-05 10:39 ` 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=1486183368-31664-1-git-send-email-paul.ydlee@gmail.com \
--to=paul.ydlee@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=noralf@tronnes.org \
--cc=thomas.petazzoni@free-electrons.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
all inboxes | Powered by JetHome®