From: Akira Yokosawa <akiyks@gmail.com>
To: jani.nikula@linux.intel.com, didi.debian@cknow.org
Cc: corbet@lwn.net, dwaipayanray1@gmail.com, joe@perches.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
lukas.bulwahn@gmail.com, Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH] docs: dev-tools: checkpatch: Add targets for checkpatch tags
Date: Mon, 13 May 2024 20:51:31 +0900 [thread overview]
Message-ID: <56da5a74-be65-4f36-8d78-7423e11f537d@gmail.com> (raw)
In-Reply-To: <87a5kuez97.fsf@intel.com>
On Mon, 13 May 2024 14:18:28 +0300, Jani Nikula wrote:
> On Mon, 13 May 2024, Diederik de Haas <didi.debian@cknow.org> wrote:
>> Make the tags directly linkable by defining targets for them.
>>
>> Closes: https://lore.kernel.org/r/8090211.0vHzs8tI1a@bagend/
>> Signed-off-by: Diederik de Haas <didi.debian@cknow.org>
>> ---
>> Documentation/dev-tools/checkpatch.rst | 216 +++++++++++++++++++++++++
>> 1 file changed, 216 insertions(+)
>>
>> diff --git a/Documentation/dev-tools/checkpatch.rst b/Documentation/dev-tools/checkpatch.rst
>> index 127968995847..6499e29c3a19 100644
>> --- a/Documentation/dev-tools/checkpatch.rst
>> +++ b/Documentation/dev-tools/checkpatch.rst
>> @@ -242,6 +242,8 @@ This section contains a description of all the message types in checkpatch.
>> Allocation style
>> ----------------
>>
>> + .. _alloc-array-args:
>> +
>> **ALLOC_ARRAY_ARGS**
>
> Alternatively, you could just convert the definition lists into section
> titles to make them implicit hyperlink targets. The rst stays cleaner
> and there's no manual updating.
>
+1
I misread Diederik's intention and thought he wanted that single target
he mentioned in the other thread.
I believe Jani's suggestion is the right way going forward.
Thanks, Akira
> BR,
> Jani.
[snip]
next prev parent reply other threads:[~2024-05-13 11:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 10:22 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
2024-05-13 11:51 ` Akira Yokosawa [this message]
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=56da5a74-be65-4f36-8d78-7423e11f537d@gmail.com \
--to=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=didi.debian@cknow.org \
--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 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®