From: Dan Carpenter <dan.carpenter@linaro.org>
To: Ashok Kumar <ashokemailat@yahoo.com>
Cc: Julia Lawall <julia.lawall@inria.fr>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
"linux-staging@lists.linux.dev" <linux-staging@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"outreachy@lists.linux.dev" <outreachy@lists.linux.dev>
Subject: Re: [PATCH] staging: fb_tinylcd Alignment to open parenthesis
Date: Sat, 4 May 2024 14:17:59 +0300 [thread overview]
Message-ID: <45366e52-47e7-4e9d-a2a2-7eede9d3b450@moroto.mountain> (raw)
In-Reply-To: <1389558595.6771301.1714753224419@mail.yahoo.com>
On Fri, May 03, 2024 at 04:20:24PM +0000, Ashok Kumar wrote:
>
> Is there a list of exceptions to the checkpatch information that we can ignore in general.
>
For Greg's subsystems ignore the warning about extra parentheses.
You can search on lore for if a patch has been patch has been sent
before. Otherwise ignore checkpatch if it tells you to do something
that makes the code less readable.
regards,
dan carpenter
prev parent reply other threads:[~2024-05-04 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ZjRDUO6/M+RDCcQJ.ref@c>
2024-05-03 1:52 ` [PATCH] staging: fb_tinylcd Alignment to open parenthesis Ashok Kumar
2024-05-03 5:11 ` Dan Carpenter
2024-05-03 6:54 ` Julia Lawall
2024-05-03 16:20 ` Ashok Kumar
2024-05-04 11:17 ` Dan Carpenter [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=45366e52-47e7-4e9d-a2a2-7eede9d3b450@moroto.mountain \
--to=dan.carpenter@linaro.org \
--cc=ashokemailat@yahoo.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@inria.fr \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).