From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Khaled Elnaggar <khaledelnaggarlinux@gmail.com>,
linux-doc@vger.kernel.org
Cc: willy@infradead.org, linux-kernel-mentees@lists.linux.dev,
shuah@kernel.org, corbet@lwn.net, linux-kernel@vger.kernel.org,
masahiroy@kernel.org
Subject: Re: [PATCH v2] docs: symbol-namespaces: fix reST warning with literal block
Date: Wed, 4 Jun 2025 16:16:01 +0700 [thread overview]
Message-ID: <aEAO0VFSuIIKH8Pn@archie.me> (raw)
In-Reply-To: <20250526211039.163449-1-khaledelnaggarlinux@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 775 bytes --]
On Tue, May 27, 2025 at 12:10:39AM +0300, Khaled Elnaggar wrote:
> diff --git a/Documentation/core-api/symbol-namespaces.rst b/Documentation/core-api/symbol-namespaces.rst
> index f7cfa7b73e97..32fc73dc5529 100644
> --- a/Documentation/core-api/symbol-namespaces.rst
> +++ b/Documentation/core-api/symbol-namespaces.rst
> @@ -85,7 +85,7 @@ namespace cannot be imported.
> The macro takes a comma separated list of module names, allowing only those
> modules to access this symbol. Simple tail-globs are supported.
>
> -For example:
> +For example::
>
> EXPORT_SYMBOL_GPL_FOR_MODULES(preempt_notifier_inc, "kvm,kvm-*")
>
LGTM, thanks!
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-06-04 9:16 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
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 [this message]
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=aEAO0VFSuIIKH8Pn@archie.me \
--to=bagasdotme@gmail.com \
--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 \
--cc=willy@infradead.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).