linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Khaled Elnaggar <khaledelnaggarlinux@gmail.com>
Cc: linux-doc@vger.kernel.org, linux-kernel-mentees@lists.linux.dev,
	shuah@kernel.org, corbet@lwn.net, masahiroy@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: escape literal asterisk to fix reST emphasis warning
Date: Mon, 26 May 2025 20:35:17 +0100	[thread overview]
Message-ID: <aDTCdQNUN4Zlw2jJ@casper.infradead.org> (raw)
In-Reply-To: <20250526184401.33417-1-khaledelnaggarlinux@gmail.com>

On Mon, May 26, 2025 at 09:43:59PM +0300, Khaled Elnaggar wrote:
> Escaped a literal '*' character in symbol-namespaces.rst to prevent
> a Docutils warning about unmatched emphasis markers during documentation build.

I don't think this is the right way to fix this problem.  We want
the test to work in both rendered and un-rendered form.  I think
we can do something like:

-For example:
+For example::

to turn it into a block that is rendered literally.  See

                For example::

                  echo $((100 * `cat active_duration` / `cat connected_duration`))

as an example in Documentation/ABI/stable/sysfs-bus-usb

>  For example:
> 
> -  EXPORT_SYMBOL_GPL_FOR_MODULES(preempt_notifier_inc, "kvm,kvm-*")
> +  EXPORT_SYMBOL_GPL_FOR_MODULES(preempt_notifier_inc, "kvm,kvm-\*")
> 
>  will limit usage of this symbol to modules whoes name matches the given
>  patterns.
> --
> 2.47.2
> 
> 

  reply	other threads:[~2025-05-26 19:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-26 18:43 [PATCH] docs: escape literal asterisk to fix reST emphasis warning Khaled Elnaggar
2025-05-26 19:35 ` Matthew Wilcox [this message]
2025-05-26 20:23   ` Khaled Elnaggar
2025-05-26 21:10 ` [PATCH v2] docs: symbol-namespaces: fix reST warning with literal block Khaled Elnaggar
2025-06-04  9:16   ` Bagas Sanjaya
2025-06-05 19:38   ` Masahiro Yamada

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=aDTCdQNUN4Zlw2jJ@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=corbet@lwn.net \
    --cc=khaledelnaggarlinux@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel-mentees@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=shuah@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).