From: Joe Perches <joe@perches.com>
To: "B K Karthik" <bkkarthik@pesu.pes.edu>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jan Sebastian Götte" <linux@jaseg.net>,
"Nicolas Saenz Julienne" <nsaenzjulienne@suse.de>,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fbtft-bus.c: Removing that prohibited space before ')'
Date: Fri, 26 Jun 2020 22:12:35 -0700 [thread overview]
Message-ID: <82612d7cc05d1a8f178a71be25884ec8ac5ef6cc.camel@perches.com> (raw)
In-Reply-To: <20200627045150.ysqvd47o52f4a6rc@pesu-pes-edu>
On Sat, 2020-06-27 at 00:51 -0400, B K Karthik wrote:
> fbtft-bus.c:
>
> fixing ERROR: space prohibited before that close parenthesis ')' by removing that space and ',' in line 65 and 67.
[]
> 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)
Q: Did you compile the files modified by this patch
before you submitted it?
A: No
next prev parent reply other threads:[~2020-06-27 5:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-27 4:51 B K Karthik
2020-06-27 5:12 ` Joe Perches [this message]
2020-06-27 5:12 ` Greg Kroah-Hartman
2020-06-27 23:53 ` kernel test robot
2020-06-29 0:29 ` kernel test robot
2020-07-09 13:13 ` 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=82612d7cc05d1a8f178a71be25884ec8ac5ef6cc.camel@perches.com \
--to=joe@perches.com \
--cc=bkkarthik@pesu.pes.edu \
--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=linux@jaseg.net \
--cc=nsaenzjulienne@suse.de \
/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®