linux-kernel-mentees.lists.linuxfoundation.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Dwaipayan Ray <dwaipayanray1@gmail.com>,
	Jonathan Corbet <corbet@lwn.net>,
	 Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-kernel-mentees@lists.linuxfoundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 0/2] checkpatch: add verbose mode
Date: Thu, 25 Feb 2021 09:33:40 -0800	[thread overview]
Message-ID: <bcee822d1934772f47702ee257bc735c8f467088.camel@perches.com> (raw)
In-Reply-To: <20210222075205.19834-1-dwaipayanray1@gmail.com>

On Mon, 2021-02-22 at 13:22 +0530, Dwaipayan Ray wrote:
> Add a new verbose mode to checkpatch. The verbose test
> descriptions are read from the checkpatch documentation
> file at `Documentation/dev-tools/checkpatch.rst`.
> 
> The verbose mode is optional and can be enabled by the
> flag -v or --verbose.
> 
> The documentation file is only parsed by checkpatch.pl
> if the verbose mode is enabled. The verbose mode can
> not be used together with the --terse option.

I don't have any real objection to this patch set, but as this
might be added to the Documentation tree and in .rst format,
perhaps Jonathan Corbet and/or Mauro Carvalho Chehab might have
some opinion.

Also I do not want to be a maintainer of this .rst file and
likely neither Jon nor Mauro would either.  Perhaps you?

Ideally, the patch order would be reversed so the .rst file
is added first, then checkpatch updated to use it.

And _a lot_ more types and descriptive content should be added.

> 
> Changes in v7:
> - Add color coding support to --list-types option
> 
> Changes in v6:
> - Allow using verbose mode with --list-types option
> 
> Changes in v5:
> - Change the reference format to use absolute links.
> - Print verbose descriptions only for the first time
>   a message type is encountered.
> 
> Changes in v4:
> - Change the type description format
> - Group the message types by usage
> - Make handling of --terse with --verbose simpler
> 
> Changes in v3:
> - Simplify documentation file parsing in checkpatch
> - Document a total of 33 message types for checkpatch
> 
> Changes in v2:
> - Use .rst Field Lists to specify the type descriptions.
> - Add a few more type descriptions to documentation.
> 
> Dwaipayan Ray (2):
>   checkpatch: add verbose mode
>   docs: add documentation for checkpatch
> 
>  Documentation/dev-tools/checkpatch.rst | 525 +++++++++++++++++++++++++
>  Documentation/dev-tools/index.rst      |   1 +
>  scripts/checkpatch.pl                  | 133 ++++++-
>  3 files changed, 639 insertions(+), 20 deletions(-)
>  create mode 100644 Documentation/dev-tools/checkpatch.rst
> 


_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees

  parent reply	other threads:[~2021-02-25 17:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22  7:52 [Linux-kernel-mentees] [PATCH v7 0/2] checkpatch: add verbose mode Dwaipayan Ray
2021-02-22  7:52 ` [Linux-kernel-mentees] [PATCH v7 1/2] " Dwaipayan Ray
2021-02-22  7:52 ` [Linux-kernel-mentees] [PATCH v7 2/2] docs: add documentation for checkpatch Dwaipayan Ray
2021-02-25 17:33 ` Joe Perches [this message]
2021-02-25 18:08   ` [PATCH v7 0/2] checkpatch: add verbose mode Dwaipayan Ray
2021-02-25 20:55     ` Mauro Carvalho Chehab
2021-02-26 10:50       ` Joe Perches
2021-02-25 21:16     ` Jonathan Corbet
2021-02-26  8:53       ` Dwaipayan Ray
2021-02-26  5:59     ` Lukas Bulwahn
2021-02-26  9:20       ` 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=bcee822d1934772f47702ee257bc735c8f467088.camel@perches.com \
    --to=joe@perches.com \
    --cc=corbet@lwn.net \
    --cc=dwaipayanray1@gmail.com \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@kernel.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;
as well as URLs for NNTP newsgroup(s).