The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Dwaipayan Ray <dwaipayanray1@gmail.com>
To: joe@perches.com
Cc: linux-kernel-mentees@lists.linuxfoundation.org,
	lukas.bulwahn@gmail.com, linux-kernel@vger.kernel.org,
	Dwaipayan Ray <dwaipayanray1@gmail.com>
Subject: [PATCH RFC 0/3] checkpatch: add verbose mode
Date: Wed, 27 Jan 2021 00:05:18 +0530	[thread overview]
Message-ID: <20210126183521.26535-1-dwaipayanray1@gmail.com> (raw)

This patch series adds a verbose mode to checkpatch.
The verbose test descriptions are loaded from the
checkpatch documentation and parsed by checkpatch.

The documentation itself needs more work. More input
on the usage and test descriptions are needed.

Also the visual aspects of the verbose mode needs
some work put into. The usual printing of verbose
descriptions can cause confusion and maybe hard to
distinguish from the actual warnings.

Please note that this is only an initial attempt
and any comments are welcome.

Dwaipayan Ray (3):
  checkpatch: add verbose mode
  docs: add documentation for checkpatch
  docs: add documentation for checkpatch

 Documentation/dev-tools/checkpatch.rst | 283 +++++++++++++++++++++++++
 Documentation/dev-tools/index.rst      |   1 +
 scripts/checkpatch.pl                  |  55 +++++
 3 files changed, 339 insertions(+)
 create mode 100644 Documentation/dev-tools/checkpatch.rst

-- 
2.30.0


             reply	other threads:[~2021-01-27  1:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-26 18:35 Dwaipayan Ray [this message]
2021-01-26 18:35 ` [PATCH RFC 1/3] checkpatch: add verbose mode Dwaipayan Ray
2021-01-26 20:11   ` Joe Perches
2021-01-26 20:27     ` Dwaipayan Ray
2021-01-26 22:44       ` Joe Perches
2021-01-26 18:35 ` [PATCH RFC 2/3] docs: add documentation for checkpatch Dwaipayan Ray
2021-01-26 18:35 ` [PATCH RFC 3/3] " Dwaipayan Ray

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=20210126183521.26535-1-dwaipayanray1@gmail.com \
    --to=dwaipayanray1@gmail.com \
    --cc=joe@perches.com \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --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