From: Alaa Emad <alaaemadhossney.ae@gmail.com>
To: gregkh@linuxfoundation.org, mh12gx2825@gmail.com,
alaaemadhossney.ae@gmail.com, sbrivio@redhat.com,
colin.king@canonical.com, oliver.graute@kococonnector.com
Cc: dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH] Fix space prohibited issue in fbtft-bus.c
Date: Fri, 12 Feb 2021 16:58:33 +0200 [thread overview]
Message-ID: <20210212145833.3809-1-alaaemadhossney.ae@gmail.com> (raw)
This change fixes a checkpatch error for "space prohibited before that close parenthesis ')'"
Signed-off-by: Alaa Emad <alaaemadhossney.ae@gmail.com>
---
certs/x509_revocation_list | 0
drivers/staging/fbtft/fbtft-bus.c | 4 ++--
2 files changed, 2 insertions(+), 2 deletions(-)
create mode 100644 certs/x509_revocation_list
diff --git a/certs/x509_revocation_list b/certs/x509_revocation_list
new file mode 100644
index 000000000000..e69de29bb2d1
diff --git a/drivers/staging/fbtft/fbtft-bus.c b/drivers/staging/fbtft/fbtft-bus.c
index 63c65dd67b17..847cbfbbd766 100644
--- a/drivers/staging/fbtft/fbtft-bus.c
+++ b/drivers/staging/fbtft/fbtft-bus.c
@@ -62,9 +62,9 @@ out: \
} \
EXPORT_SYMBOL(func);
-define_fbtft_write_reg(fbtft_write_reg8_bus8, u8, u8, )
+define_fbtft_write_reg(fbtft_write_reg8_bus8, u8, u8)
define_fbtft_write_reg(fbtft_write_reg16_bus8, __be16, u16, cpu_to_be16)
-define_fbtft_write_reg(fbtft_write_reg16_bus16, u16, u16, )
+define_fbtft_write_reg(fbtft_write_reg16_bus16, u16, u16)
void fbtft_write_reg8_bus9(struct fbtft_par *par, int len, ...)
{
--
2.25.1
next reply other threads:[~2021-02-12 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 14:58 Alaa Emad [this message]
2021-02-12 15:02 ` [PATCH] Fix space prohibited issue in fbtft-bus.c Greg KH
2021-02-12 23:16 ` kernel test robot
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=20210212145833.3809-1-alaaemadhossney.ae@gmail.com \
--to=alaaemadhossney.ae@gmail.com \
--cc=colin.king@canonical.com \
--cc=devel@driverdev.osuosl.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mh12gx2825@gmail.com \
--cc=oliver.graute@kococonnector.com \
--cc=sbrivio@redhat.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).