From: Joe Perches <joe@perches.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Andy Whitcroft <apw@canonical.com>
Subject: Re: Anyone have ideas for checkpatch improvements ?
Date: Sun, 24 Jan 2021 17:59:15 -0800 [thread overview]
Message-ID: <53c071a4fc34b1bf5a655cc468837b4fbe6f6787.camel@perches.com> (raw)
In-Reply-To: <08ee32211e8b40234257a236c842a7be6703144c.camel@perches.com>
One of the linux-mentees, Dwaipayan Ray, asked me in a private
email for ideas for improvements to checkpatch.
Though I am not his nominal mentor, my response to him was the below.
Does anyone have any more ideas for checkpatch improvements or
enhancements?
---
On Fri, 2021-01-15 at 21:02 +0530, Dwaipayan Ray wrote:
> I am actually writing to you
> regarding any possible ideas for checkpatch or any improvements
> you would like to see moving forward with checkpatch.
>
> The last time you had suggested about --fix options. But as we saw
> that maybe some places are better off with it. So do you have
> anything particular in mind?
>
> Again, thanks a lot in advance. Since my mentorship will go on till
> about march, I am indeed in dire need of ideas.
You could:
o Separate the various tests into individual modules that are aggregated
at startup.
o Create a test suite.
o Externally document the thing with use cases, all the named tests
are not particularly documented.
o Add --verbose test descriptions, so 'why this message is emitted'
description is optionally available to / understood by the user.
o Add support for various brace location / required spacing styles.
prev parent reply other threads:[~2021-01-25 2:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 1:55 Joe Perches
2021-01-25 1:59 ` 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=53c071a4fc34b1bf5a655cc468837b4fbe6f6787.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 \
/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®