All of lore.kernel.org
 help / color / mirror / Atom feed
From: "小笠原 共志" <sawara04.o@gmail.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: gregkh@linuxfoundation.org, dri-devel@lists.freedesktop.org,
	 linux-fbdev@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: fbtft: Fix "space prohibited before that close parenthesis ')'" error reported by checkpatch
Date: Thu, 22 Feb 2024 22:38:11 +0900	[thread overview]
Message-ID: <CAKNDObDWgkpzfHMBkQA3F3O-Qt6Q8UJ8BJufzYz72d9TK4qaKA@mail.gmail.com> (raw)
In-Reply-To: <87f76339-3ace-4cbe-bdb9-266a86bf55eb@moroto.mountain>

[-- Attachment #1: Type: text/plain, Size: 791 bytes --]

> This breaks the build.  You could do a search for it.
>
> https://lore.kernel.org/all/?q=define_fbtft_write_reg

I understand. Thanks for letting me know.

2024年2月21日(水) 19:18 Dan Carpenter <dan.carpenter@linaro.org>:

> On Wed, Feb 21, 2024 at 06:54:04PM +0900, sawara04.o@gmail.com wrote:
> > From: Kyoji Ogasawara <sawara04.o@gmail.com>
> >
> > Since whitespace is prohibited before that close parenthesis ')' in a
> > conditional statements, remove it and fix checkpatch.pl error "space
> prohibited before that
> > close parenthesis ')'".
> >
> > Signed-off-by: Kyoji Ogasawara <sawara04.o@gmail.com>
>
> This breaks the build.  You could do a search for it.
>
> https://lore.kernel.org/all/?q=define_fbtft_write_reg
>
> regards,
> dan carpenter
>
>

[-- Attachment #2: Type: text/html, Size: 1681 bytes --]

      reply	other threads:[~2024-02-22 13:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-21  9:54 [PATCH] staging: fbtft: Fix "space prohibited before that close parenthesis ')'" error reported by checkpatch sawara04.o
2024-02-21 10:18 ` Dan Carpenter
2024-02-22 13:38   ` 小笠原 共志 [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=CAKNDObDWgkpzfHMBkQA3F3O-Qt6Q8UJ8BJufzYz72d9TK4qaKA@mail.gmail.com \
    --to=sawara04.o@gmail.com \
    --cc=dan.carpenter@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.