From: Diederik de Haas <didi.debian@cknow.org>
To: Jani Nikula <jani.nikula@linux.intel.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Dwaipayan Ray <dwaipayanray1@gmail.com>,
Joe Perches <joe@perches.com>, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: dev-tools: checkpatch: Add targets for checkpatch tags
Date: Mon, 13 May 2024 16:48:13 +0200 [thread overview]
Message-ID: <32373229.FC8mGFU5Tv@bagend> (raw)
In-Reply-To: <CAKXUXMzw6_JnPxXfgU2tEU-VkU6E_=ee-V4MUzGX8MQCSXLuNA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 525 bytes --]
On Monday, 13 May 2024 13:46:39 CEST Lukas Bulwahn wrote:
> It is important to check that the verbose option of
> the checkpatch still works. The script actually parses the
> documentation and then shows the relevant parts as verbose output to
> the user.
I wasn't aware of that functionality as I've mostly used ``--terse``.
What I want(ed) is having the documentation for a tag easily accessible.
But it doesn't get much better then it already being part of the tool.
IOW: Please disregard this patch.
Cheers,
Diederik
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-05-13 14:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 10:22 [PATCH] docs: dev-tools: checkpatch: Add targets for checkpatch tags Diederik de Haas
2024-05-13 11:18 ` Jani Nikula
2024-05-13 11:46 ` Lukas Bulwahn
2024-05-13 13:45 ` Diederik de Haas
2024-05-13 14:48 ` Diederik de Haas [this message]
2024-05-13 11:51 ` Akira Yokosawa
2024-05-13 13:13 ` Jonathan Corbet
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=32373229.FC8mGFU5Tv@bagend \
--to=didi.debian@cknow.org \
--cc=corbet@lwn.net \
--cc=dwaipayanray1@gmail.com \
--cc=jani.nikula@linux.intel.com \
--cc=joe@perches.com \
--cc=linux-doc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.