From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jan Kara <jack@suse.cz>, Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] fs: porting.rst: use literal string to avoid warning
Date: Mon, 16 Nov 2026 10:06:57 +0700 [thread overview]
Message-ID: <avpzSippbZRkaki9@archie.me> (raw)
In-Reply-To: <hyk4puvpheleitf4kt74aamqex2ytuxpda2iki5bgzoteldf23@pccvy6sdmerx>
[-- Attachment #1: Type: text/plain, Size: 950 bytes --]
On Fri, Sep 25, 2026 at 11:32:43AM +0200, Jan Kara wrote:
> On Thu 24-09-26 11:39:15, Randy Dunlap wrote:
> > Avoid the docutils warning:
> >
> > Documentation/filesystems/porting.rst:1417: WARNING: Inline emphasis start-string without end-string. [docutils]
> >
> > by quoting the const pointer in literal quotation marks.
> > (Adding a space between the '*' and the '.' also works but it looks odd.)
> >
> > Reported-by: kernel test robot <lkp@intel.com>
> > Closes: https://lore.kernel.org/oe-kbuild-all/202609231806.ILZP6Fy0-lkp@intel.com/
> > Fixes: 025756ee7b47 ("fs: port mnt_idmap() and file_mnt_idmap() to const mnt_idmap")
> > Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
>
> Thanks! Looks good. Feel free to add:
>
> Reviewed-by: Jan Kara <jack@suse.cz>
I still see the warning on current docs-next, though. Has the patch not
been applied yet?
--
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:[~2026-11-16 3:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 18:39 [PATCH] fs: porting.rst: use literal string to avoid warning Randy Dunlap
2026-09-25 9:32 ` Jan Kara
2026-11-16 3:06 ` Bagas Sanjaya [this message]
2026-11-16 6:39 ` Randy Dunlap
2026-11-16 8:11 ` Bagas Sanjaya
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=avpzSippbZRkaki9@archie.me \
--to=bagasdotme@gmail.com \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=jack@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=viro@zeniv.linux.org.uk \
/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.