From: Greg KH <gregkh@linuxfoundation.org>
To: carlosteniswarrior@gmail.com
Cc: linux@jaseg.net, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: fbtft : fbtft-bus: fixed two checkpatch errors
Date: Tue, 14 Apr 2020 10:25:06 +0200 [thread overview]
Message-ID: <20200414082506.GB10645@kroah.com> (raw)
In-Reply-To: <20200414073047.2757-1-carlosteniswarrior@gmail.com>
On Tue, Apr 14, 2020 at 09:30:47AM +0200, carlosteniswarrior@gmail.com wrote:
> From: Carlos Guerrero Álvarez <carlosteniswarrior@gmail.com>
>
> Fixed two checkpatch space prohibited before that close parenthesis errors.
>
> Signed-off-by: Carlos Guerrero Álvarez <carlosteniswarrior@gmail.com>
> ---
> drivers/staging/fbtft/fbtft-bus.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/fbtft/fbtft-bus.c b/drivers/staging/fbtft/fbtft-bus.c
> index 63c65dd67b17..cdb451dd3fde 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,)
If I remember correct, the original code here is required, due to how
some older versions of gcc works.
Did you test-build this? Did it work properly?
I would just leave this alone,
greg k-h
prev parent reply other threads:[~2020-04-14 8:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 7:30 carlosteniswarrior
2020-04-14 8:25 ` Greg KH [this message]
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=20200414082506.GB10645@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=carlosteniswarrior@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@jaseg.net \
/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®