From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: krishnanand G <krishnanandgeetheswaran@gmail.com>
Cc: andy@kernel.org, dri-devel@lists.freedesktop.org,
linux-fbdev@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: fbtft: fix spacing in macro calls
Date: Sun, 27 Sep 2026 18:41:25 +0200 [thread overview]
Message-ID: <2026092758-salary-wheat-735e@gregkh> (raw)
In-Reply-To: <CAG_41B+424_C5FA0PX9g1pDEPz2WX8JSeFhTWFpJ2TWgWLQjBw@mail.gmail.com>
On Sat, Sep 26, 2026 at 08:02:38PM +0530, krishnanand G wrote:
> The two calls to define_fbtft_write_reg() that use the default
> modifier have a space before the closing parenthesis. This triggers
> two checkpatch.pl errors.
>
> Add an inline comment for the intentionally empty modifier argument.
> It satisfies the spacing check without changing the macro expansion.
>
> Tests: scripts/checkpatch.pl --no-tree -f --terse --strict
> drivers/staging/fbtft/fbtft-bus.c
>
> A full kernel build was not run because the sparse checkout does not
> include the architecture makefiles.
Do not ever work with sparse checkouts,that's not how to do kernel
development.
> Signed-off-by: Krishnanand G <
> 118352827+Krishnanand-G@users.noreply.github.com>
There is no patch here :(
next parent reply other threads:[~2026-09-27 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAG_41B+424_C5FA0PX9g1pDEPz2WX8JSeFhTWFpJ2TWgWLQjBw@mail.gmail.com>
2026-09-27 16:41 ` gregkh [this message]
2026-09-27 9:48 [PATCH] staging: fbtft: fix spacing in macro calls krishnanand G
2026-09-27 16:40 ` Greg KH
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=2026092758-salary-wheat-735e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andy@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=krishnanandgeetheswaran@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox