mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Jonathan Corbet <corbet@lwn.net>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 4/5] docs: kernel-doc.rst: don't let automarkup mangle with consts
Date: Sun, 23 Nov 2025 19:41:18 -0800	[thread overview]
Message-ID: <52ca6fd7-9286-4d8d-8611-644d38d79484@infradead.org> (raw)
In-Reply-To: <f68f2da2a5eb1508c4c56b8f59719773b84b146b.1763814816.git.mchehab+huawei@kernel.org>



On 11/22/25 4:37 AM, Mauro Carvalho Chehab wrote:
> This document contains several words that tricks automarkup.
> 
> Ensure that all of them will be inside a ``const`` markup,
> avoiding automarkup to touch them.
> 
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> ---
>  Documentation/doc-guide/kernel-doc.rst | 25 +++++++++++++------------
>  1 file changed, 13 insertions(+), 12 deletions(-)

Reviewed-by: Randy Dunlap <rdunlap@infradead.org>

Thanks.

-- 
~Randy

  reply	other threads:[~2025-11-24  3:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-22 12:37 [PATCH v4 0/5] kernel-doc: add support for documenting vars Mauro Carvalho Chehab
2025-11-22 12:37 ` [PATCH v4 1/5] kernel-doc: add support for handling global variables Mauro Carvalho Chehab
2025-11-22 12:37 ` [PATCH v4 2/5] kernel-doc: add support to handle DEFINE_ variables Mauro Carvalho Chehab
2025-11-22 12:37 ` [PATCH v4 3/5] docs: media: v4l2-ioctl.h: document two global variables Mauro Carvalho Chehab
2025-11-22 12:37 ` [PATCH v4 4/5] docs: kernel-doc.rst: don't let automarkup mangle with consts Mauro Carvalho Chehab
2025-11-24  3:41   ` Randy Dunlap [this message]
2025-11-22 12:37 ` [PATCH v4 5/5] docs: kernel-doc.rst: document the new "var" kernel-doc markup Mauro Carvalho Chehab
2025-11-23 11:28 ` [PATCH v4 0/5] kernel-doc: add support for documenting vars Akira Yokosawa

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=52ca6fd7-9286-4d8d-8611-644d38d79484@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@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
all inboxes | Powered by JetHome®