From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: wrmfwv@163.com
Cc: andy@kernel.org, gregkh@linuxfoundation.org,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
gtl-m <admin@micronull.cn>
Subject: Re: [PATCH] staging: fbtft: fix syntax errors in macros
Date: Mon, 19 Oct 2026 12:20:51 +0300 [thread overview]
Message-ID: <atXg85m8ukjFuok_@ashevche-desk.local> (raw)
In-Reply-To: <20261018085345.17619-1-wrmfwv@163.com>
On Sun, Oct 18, 2026 at 04:53:45PM +0800, wrmfwv@163.com wrote:
> checkpatch.pl reported errors regarding unnecessary commas and spaces
> before closing parentheses in the fbtft_write_reg macro definitions.
> Remove them to strictly comply with the kernel coding style guidelines.
NAK.
It's your homework to understand why.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-10-19 9:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 8:53 wrmfwv
2026-10-18 9:54 ` Greg KH
2026-10-19 9:20 ` Andy Shevchenko [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=atXg85m8ukjFuok_@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=admin@micronull.cn \
--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 \
--cc=wrmfwv@163.com \
/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®