From: Joe Perches <joe@perches.com>
To: Manuel Ebner <manuelebner@mailbox.org>,
Andy Whitcroft <apw@canonical.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] checkpatch: Introduce a check for the nesting of brackets
Date: Tue, 23 Jun 2026 12:20:23 -0700 [thread overview]
Message-ID: <5bcdddfba2d575e78a548359c9c882e06a3a558f.camel@perches.com> (raw)
In-Reply-To: <20260623190937.47435-3-manuelebner@mailbox.org>
On Tue, 2026-06-23 at 21:09 +0200, Manuel Ebner wrote:
> I have a local script that checks files for the right nesting of brackets.
> With the help of the script I managed to do a couple patches [1]. Unfortunately
> there are (still) a lot of false positives [2]. I do not filter false positives
> (yet).
>
> To simplify testing the new check is enabled and warns(WARN()). The final
> version would be disabled by default and would trigger CHK().
>
> Would this addition, if cleaned up, get into checkpatch.pl?
probably not as it's not suitable for patches.
prev parent reply other threads:[~2026-06-23 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 19:09 Manuel Ebner
2026-06-23 19:20 ` Joe Perches [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=5bcdddfba2d575e78a548359c9c882e06a3a558f.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=dwaipayanray1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=manuelebner@mailbox.org \
/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®