From: Matteo Croce <technoboy85@gmail.com>
To: kernel test robot <lkp@intel.com>, Joe Perches <joe@perches.com>
Cc: oe-kbuild-all@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 8662/12838] htmldocs: MAINTAINERS:40: WARNING: Inline strong start-string without end-string. [docutils]
Date: Thu, 9 Apr 2026 12:12:57 +0200 [thread overview]
Message-ID: <CAFnufp29D4VdTgoJ4uDk-dQ4-RuO_C6=TQ7O9TA5M=JSe1j+cw@mail.gmail.com> (raw)
In-Reply-To: <202604090741.1kUVXMoc-lkp@intel.com>
Il giorno gio 9 apr 2026 alle ore 07:24 kernel test robot
<lkp@intel.com> ha scritto:
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: db7efce4ae23ad5e42f5f55428f529ff62b86fab
> commit: 420849332f9f9f1ce6ff142868ae2e6ae9f98f65 [8662/12838] get_maintainer: add ** glob pattern support
> compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
> docutils: docutils (Docutils 0.21.2, Python 3.13.5, on linux)
> reproduce: (https://download.01.org/0day-ci/archive/20260409/202604090741.1kUVXMoc-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202604090741.1kUVXMoc-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> Checksumming on output with GSO
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [docutils]
> >> MAINTAINERS:40: WARNING: Inline strong start-string without end-string. [docutils]
> Documentation/userspace-api/landlock:480: ./security/landlock/errata/abi-4.h:5: ERROR: Unexpected section title.
>
>
The problem is that "**" is seen as start of a bold text in RST.
Escaping the first * fixes error and keeps the glob unaffected:
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -35,7 +35,7 @@ Descriptions of section entries and preferred order
F: drivers/net/ all files in and below drivers/net
F: drivers/net/* all files in drivers/net, but not below
F: */net/* all files in "any top level directory"/net
- F: fs/**/*foo*.c all *foo*.c files in any subdirectory of fs
+ F: fs/\**/*foo*.c all *foo*.c files in any subdirectory of fs
One pattern per line. Multiple F: lines acceptable.
X: *Excluded* files and directories that are NOT maintained, same
rules as F:. Files exclusions are tested before file matches.
should I create a fix patch or we can still amend the previous in net-next?
Regards,
--
Matteo Croce
perl -e 'for($t=0;;$t++){print chr($t*($t>>8|$t>>13)&255)}' |aplay
prev parent reply other threads:[~2026-04-09 10:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 5:24 kernel test robot
2026-04-09 10:12 ` Matteo Croce [this message]
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='CAFnufp29D4VdTgoJ4uDk-dQ4-RuO_C6=TQ7O9TA5M=JSe1j+cw@mail.gmail.com' \
--to=technoboy85@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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