mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Lee <eric.lee0305@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Andy Shevchenko <andy@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: fbtft: fix space prohibited before that close parenthesis
Date: Tue, 3 Nov 2026 08:07:31 +0800	[thread overview]
Message-ID: <D7B3C1FA-32F4-4771-BC2D-F97D07CBFFE5@gmail.com> (raw)
In-Reply-To: <CAHp75VcvKkOmFTtJDHuKCNVUMXgjZLiNqmGcHFKT__dtTt_QJg@mail.gmail.com>

On Nov 3, 2026, at 04:44, Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> 
> It's not a fix, it does not fix anything.
> Also study the mailing list archive (lore.kernel.org) to see what
> happened to the similar patches in the past.

Thanks for your feedback. I did check the mailing list archive for the same
Checkpatch error in staging/fbtft.

They either removed the extra space between ‘,’ and ‘)’ that caused another
checkpatch error “space required after that ‘,’”,
or removed both ‘,’ and extra space before ‘)’ that caused build error.

The key difference in my change here is to make that argument “modifier” as
variable argument, not a positional argument anymore. After that, I could
safely remove both ‘,’ and extra space before  ‘)’, without further checkpatch
error.

It passed my build and verificaton based on the file "fbtft-bus.i”.

It is fine for me if you think that it is not worth removing that checkpatch error.

--
Best Regard,
Eric LI

      reply	other threads:[~2026-11-03  0:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-31  4:23 Eric LI
2026-11-02 20:44 ` Andy Shevchenko
2026-11-03  0:07   ` Eric Lee [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=D7B3C1FA-32F4-4771-BC2D-F97D07CBFFE5@gmail.com \
    --to=eric.lee0305@gmail.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=andy@kernel.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-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 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®